Results 1 to 7 of 7

Thread: Multiuser: Database problem

  1. #1

    Thread Starter
    Addicted Member
    Join Date
    Dec 2000
    Location
    Sweden
    Posts
    155

    Multiuser: Database problem

    Hi

    I've done an application in VB6 that uses an Access db.

    My problem is that because that are several users updating the db at the same time.
    This has caused the db to crash a few times (at least I think it's the multiuser thing that causes this problem)

    Any idea on how to solve this ??

    //C

  2. #2
    I'm about to be a PowerPoster! mendhak's Avatar
    Join Date
    Feb 2002
    Location
    Ulaan Baator GooGoo: Frog
    Posts
    38,170
    Get a better database.

  3. #3
    Lively Member twistedthoughts's Avatar
    Join Date
    Oct 2002
    Location
    dxb
    Posts
    114


    I agree with mendhak!!

    But just out of curiosity, How many users access the database and how big is the db??
    Opinions Are Like Belly Buttons, Everyone Has One!

  4. #4

    Thread Starter
    Addicted Member
    Join Date
    Dec 2000
    Location
    Sweden
    Posts
    155
    4-5 users

    20 MB

    /C

  5. #5
    Banned
    Join Date
    Jul 2003
    Location
    New delhi
    Posts
    143
    hi

    when u start the updating the table


    take the isolation label of ado


    it solve your problem

    it not anything to the msacess.it is the process of ado and locking

    biswajit das

  6. #6
    Member Birth's Avatar
    Join Date
    Jan 2003
    Location
    Montreal
    Posts
    57
    Read this: http://support.microsoft.com/default...b;en-us;122958

    It certainly cured my problem. Hope it helps you!

  7. #7
    Member
    Join Date
    Apr 2003
    Posts
    37
    It is NOT the database...

    I run 50 concurrent users on DAO on MS Access. You can't tell 1 user from 50.

    No lockups, little bloat,
    100MB database accumalating 5meg/month.

    For starts, If you are, stop logging in/out every operation. Set DB object and leave them logged in until app closes or timed out for inactivity.

    We've bombarded a DB with appends/updates from 15 stations until achieved without err; test your techniques before you implement them.

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