Access DB Application Locks Up

Server seems to be locked up - possibly Lock Record symptom, but also had a case where a Text File on the server was locked by some other machine and would not even allow XCOPY to be run on that directory on the server

When the locked text file is encountered by XCOPY it simply stops copying (abandons the copy process but the machine is not actually locked up - can run other prcesses)

I could not understand how the text file could be locked on the server

I'm starting to wonder if the problem is in fact an Access problem

I have a VB6 App using Access 2000 Database. Frequently, it will lockup on some of the users machines forcing the server to be rebooted.

The server is actually just one of the PC's which shares its Access Database with 3 other users.

When one PC locks up, it causes the others to stop functioning also (because the server has stopped "serving" I guess)

Is there something I should be looking for to stop the lockups happening.

I am using ADO for the most part of the application, but still have some parts in DAO.

Appreciate any comments

I will eventually convert the whole program to run on SQL Server 2005 Express

If I do this, will I have problems using one of the PC's as the SQL Express server (running XP Pro)

OR

Is it strongly advisable to dedicate a server PC to the application running a server OS ranther than XP Pro

What benefits will say, Server 2003 give me


Thanks

maybe your problem is in your code, this is making any deadlock
see at this link

http://en.wikipedia.org/wiki/Deadlock