???So your set up is different than the others who have a BE on the server?Yes it runs fine on my PC (no server involved, but split db).
Gina, we only know what you tell us and the clearer the better.
I'm their support person, I log in remotely (Team Viewer). I am not in their office. From the beginning of my relationship with this company their system has been buggy after upgrading to Access 2013. WEIRD bugs. I've posted many here.
Thanks!
http://www.granite.ab.ca/access/perf...ldblocking.htm
That's as expected. If the program terminates abnormally the lock file may not be deleted and can cause problems. You can just delete in manually.
Are they running the program as an older version of Access but in 2013 software? Or is the db 2013 as well? I was going to suggest maybe creating a new Db and importing all over. Sometimes databases especially older ones that may have been worked on over the years gets issues that are hard to trace. The other suggestion would be to break the process apart in the program, test each step to try to pinpoint where the issue is. Make sure the queries and processes are written efficently, keys in tables, etc. Does the issue only happen when multiple people are in the program?
Yep, I've had to do that for them before.http://www.granite.ab.ca/access/perf...ldblocking.htm
That's as expected. If the program terminates abnormally the lock file may not be deleted and can cause problems. You can just delete in manually.
Thank you all so much for your suggestions. Regarding persistent locking, the database has a bound form that remains open always the "Main Process Entry", they use tabs to go to other sections, but that main form remains open. So I guess they each have a persistent connection. This is a good thing right?
I have done that (created a totally new database and imported the objects). I have a question though - the program depends heavily on macros - anyone have an opinion on this? I find them hard to follow and difficult to trace problems. I would much rather use VBA, IMHO.
That should do it!Thank you all so much for your suggestions. Regarding persistent locking, the database has a bound form that remains open always the "Main Process Entry", they use tabs to go to other sections, but that main form remains open. So I guess they each have a persistent connection. This is a good thing right?
You can go to design of form, in Database tools section at top, click on Convert Macros to VB.
???What exactly is a mass storage device?
This material from FMS may be helpful.