Results 1 to 3 of 3
  1. #1
    3 Star Lounger
    Join Date
    Nov 2001
    Location
    Brisbane, Queensland, Australia
    Posts
    330
    Thanks
    10
    Thanked 0 Times in 0 Posts

    Maintenance on split databases (Acc 97 sr2)

    I have recently joined and have been reading the post digests with interest.

    On recommendation from reading the posts, I have split my database into a front and back end. We have a 6 machine (Win95b) network with everyone having a shortcut to the front end which is on the "server" machine. This makes global changes easy as I am not part of the IT dept and have no sort of admin priveliges, (it being 1/2 a state away and we being a small side business basically left to ourselves)

    If I get a user crash, and have to replace the front end, (I keep a backup copy in a separate folder), should I use the front end to compact the "database" or should I do that directly to the back end? What other general db maintenance would you suggest?

    I am a "learn as I go" person with little formal training, but have managed to create all we have required here with help from various forum sites.
    "Heading for the deep end"

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Maintenance on split databases (Acc 97 sr2)

    Compacting the front end has no effect on the back end. You have to compact the back end separately.
    Charlotte

  3. #3
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: Maintenance on split databases (Acc 97 sr2)

    As Charlotte pointed out, compacting/repairing the frontend of a split database schema doesn't do anything to the backend.

    Aside from that, I'd strongly suggest you copy the frontend down to each users local drive and use it instead of the network version. I create a simple .bat file that includes the copy command, then create a shortcut to that file in the Startup folder. This way, each user gets a "fresh" copy of the frontend whenever they start (or reboot) their system.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

Posting Permissions

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