Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

constant error messages on network application

Status
Not open for further replies.

HebieBug

Programmer
Jan 8, 2001
354
JP
Have a *.exe file and Dll distributed amongst 10 + machines on a network. They all talk to 4 Microsoft Databases.
On my test computers it works fine with no error messages.
Works fine on the office network up to the point where more then 5 users start accessing it.
Then there will be a series of errors and once we get an error on one machine then all the applications wil get error messages and then drop off. Only way is to re open the application. Have checked Access DB and it is set to share.
The error messages are as follows
run-time error '-2147467259 (800004005)':
cannot open database". It may not be a database that your application reconizes, or the file may be corrupt
error 2:
run-time error '-2147467259(800004005)':
The database has been placed in a state by user 'Admin' on machine 'Phoenixblue' that prevents it from being opened or locked
Have already run the compact and repair database and fixed it if needed.
It looks to me that Access has a problem with more then 5 users using the database at once. Seems a little odd as when we ran the same database with Access forms it worked with no problem (a little slow though)
Anyone have a solution am thinking it might be worth just upgrading to SQL..


 
As you've discovered, MS Access isn't suited for more than a few users.

What you might want to try is the MSDE (the desktop edition of SQL Server 7.0). It's a free download to anyone who has a 6.0 development tool (VB, VC++, VFP, etc).

It's got some limitations on it (2gb max table size, single CPU only, etc.) But if you determine that you need more power, you can upgrade to the full copy of SQL 7 by simply copying your .mdf and .ldf files over.

The only downside is you would have to review all your SQL, as MS Access doesn't follow the ANSI standards all the time. Mostly it's a matter of the wildcard character used in "Like" queries. You could probably even use the Access upsizing wizard against the MSDE, which should handle a lot of the work for you.

Chip H.
 
Am not sure of the location as the company purchased the full version.
On the microsoft site there is a trial version of SQL.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top