Record locking in access XP

  • Thread starter Thread starter ToddT
  • Start date Start date
T

ToddT

Guest
Hello all,

I am a novice programmer with enough knowledge to create a database to run my small business on. Recently, as we have added XP machines to the network we have been experiencing an above average number of data issues. A "consultant" tells me to change platforms, but can never really tell me what is up with access. Can anyone suggest some record locking settings that might help this issue. If I follow the consultants logic, access is "unable" to run on a network (Split database) which effectively negates the reason for its existence.

Any experienced help would be great. Truly appreciate it.

Todd
 
Find yourself a new consultant. We'll need more details regarding the exact problems to offer advice. If you have networked PCs with different operating systems. Some running XP and others running something else, some of your problems may be caused by the ubiquitous "missing reference" problem. This manifests itself in different ways and so may not be immediatly obvious. Open a code module on a system with a problem and then go to Tools/References and make sure that no reference is marked missing. If you don't see any missing references, make sure that you have the DAO 3.6 library selected if you have DAO code in your db.
 
I have a huge article regarding this on a swell :) vba developer who researched this problem more and more since it wasn't clearly defined by the folks at MS. I'll try to find it and post it....he has code to run that can fix this problem automatically also...you can prolly put it in the startup of your db.

I'll see what I can do.

Jon
 
Thank you

Thank you both. I'm going to dig into this a little and check it out.

Todd
 
Java, that link is to an article only available to online subscribers. I am one, but our poster is probably not.
 

Users who are viewing this thread

Back
Top Bottom