Results 1 to 5 of 5
  1. #1
    4 Star Lounger
    Join Date
    Sep 2004
    Location
    Sacramento, California, USA
    Posts
    432
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Linking to BE file (Access XP)

    I have an event procedure I got from Woody's Watch that automates Access backups. I want to attach to a back end file that is used by a small user group not connected to the larger database network systems. I am wondering what event or what I can use to trigger the procedure. I though I would just use an Auto Exec macro to run it, but I discovered accessing tables from a front end does not trigger an auto exec macro. Any help would be appreciated.

    Carla

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Linking to BE file (Access XP)

    I don't quite understand what you want. Your description makes me think that you want to run code in the backend database, but the backend shouldn't contain any code, only tables.

    What exactly would you want to run, and when?

  3. #3
    4 Star Lounger
    Join Date
    Sep 2004
    Location
    Sacramento, California, USA
    Posts
    432
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Linking to BE file (Access XP)

    What I wanted to do was automate backups of a back end file. I saw a procedure in WAW that when the database file is opened it created a backup of the database file. The procedure works great. When you open the file it makes the backup file . I used a Auto Exec macro to run the procedure. I put the same procedure and macro in a back end file and do not get the same result when accessing the file from linked tables. I understand in most cases code does not go in back end files. This seemed like a simple solution for a very small database for 3 users managed by one of the users. This seemed a better strategy then hoping the user keeps current backups of the data. I am not able to teach this user all that she would need to know to manage split databases with multiple users. This setup is a management decision and my part is just to assist the user. My thought was just to have a little insurance.

    Bottom line I want the tables to have an automated backup strategy that the user does not have to be depended on to manage. I would like to have a daily backup that keeps seven days history. The network backups will not be an avenue for file retrieval, but the network drive where the tables reside can be used for storage. I do not have permissions to the network drive where the back end resides, so I have to go to the users PC to even see the tables so it is not feasible for me to personally do the backups. Any ideas or suggestions for alternatives would be great.

    Carla

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Linking to BE file (Access XP)

    The backend database doesn't run the AutoExec macro because it isn't opened, at least not in the Access interface. You could run code to back up the backend from within the frontend, for example from the frontend's AutoExec macro, or from a switchboard option. Access Watch 8-02 contains a backup routine for backends.

  5. #5
    4 Star Lounger
    Join Date
    Sep 2004
    Location
    Sacramento, California, USA
    Posts
    432
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Linking to BE file (Access XP)

    Hans,

    Exactly what I am looking for. I am a little behind in reading WAW, and this looks like a recent edition. I will now be able to get this complete on Monday.

    Carla

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •