Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2003
    Posts
    2

    Post Unanswered: Access with Windows 2000

    I have a network of about 40 users, accessing a 91mb database over lan. I have at least 30 users on windows 2k, the rest on windows xp. Server is windows 2k.

    The problem is the database becomes corrupt on a daily basis, I have upgraded windows 2k to sp4, download the jet4.0 service pack. Updated Access 2000 to sp3. Changed the registry to opportunstic locking on the server & clients.

    Is it the network switches 10/100 that is causing the problems or is it access not designed for this many users.

    Could anybody give some advise.

    thanks

    nick

  2. #2
    Join Date
    Sep 2003
    Location
    T.O.
    Posts
    326
    Does your app have a separate front and back end? If not, you have a higher chance of the db becoming corrupt with many users as it just takes one to corrupt the forms, then the db. Probably better to have separate fronts on user's local machine and back end on server. If you wanted to get really fancy, you could have unbound forms and just send a connection recordset to insert/update/delete, etc.
    All code ADO/ADOX unless otherwise specified.
    Mike.

  3. #3
    Join Date
    Sep 2003
    Posts
    2
    separate front end and back end.

    front end sits on every client pc, & back end sits on server.

Posting Permissions

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