Results 1 to 2 of 2

Thread: SYSTEM>MDW

  1. #1

    Thread Starter
    New Member
    Join Date
    Dec 2000
    Posts
    2

    Wink

    I would like to know if anyone know the answer to a very worrying predicament I'm in - I have a secured Access 2 database that I have converted to Access97 in a multi user environment (the database is used by 80 networked users - but not all at the same time!). Now and again - at least once a day at varying times - when a user tries to access the front end it gives a message saying "cannot read system.mdw - file already in use". It was suggested that not everyone is logging out of the db correctly - so messages were sent out to the users etc and also our Network team did registry updates on all relevant PCs to extend the TimeOut to 120 which they assured me would work -but I'm afraid it hasn't and I'm really at my wits end! - Please can someone help with another possible solution.

  2. #2
    Guest
    Create a vbapp that controls access to the DB. You can close the connections anywhere you want in the app, especially when they close the app, or after a timeout you set.

    You can also code to handle the specific error if the database is in use: have the app keep trying for a certain amount of time; exit with a message to the user..

Posting Permissions

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



Click Here to Expand Forum to Full Width