Software

Ask something
Discussion Locked

MS Access 2000 Behavior

0 helpful
4 replies

by thallone

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am having problems with Access2000 from a developer standpoint. As I work on a database, and put out incremental upgrades in order to get user feedback, the users are invariably experiencing problems on other machines that are not reproducable on my machine. This question is really in two parts.

First, is there anything I might be missing in settings that would cause the behavior of Access to cause errors on other machines that I cannot reproduce? I have changed the permissions so that anyone in our 40 person shop can use anything, I have set everything that I can think of to open for groups, and I have set my system to be as intolerant as possible, yet I still have problems with the occasional variable that I forgot to Explicitly declare locking on half the machines in the shop and other similat problems that do not happen at my workstation.

Secondly, and more specificaly, I am having a problem currently where after a user closes the last form in the database, the database will close, but Access will hang, unclosable except with the task manager(Win98) End Task command. Even then it takes 10 seconds or so to get the End Task Dialog. This does not happen on my machine however, no matter what I do.

So, if there's something that I can do, please let me know as soon as possible.

Jeff

4 replies

by donq

As with any database each product (or database engine) uses library files (*.dll files). Access uses many of these so your problems could vary from PC to PC depending on which and where library files are loaded on any given PC; remember your upgrade .mdb file imports a constant path based on "your" (development) machine only.

by thallone

In our shop, I have been developing on an older machine with a base install of Office2kPro. All machines with Access have the same installations, i.e. default installations. Other machines have varios levels of upgraded Office, from base, like mine,to the very latest SR1 (SP2). All other machines seem to be similarly afflicted, and only after the most recent changes (none of which did anything to the Quit process). My mose recent modifications are to a custom address list tracker that makes some tables and queries dynamically so that each employee can readily have their own list of contacts, and is not at all a part of the form that quits the application. So what do I need to check to find out why on DoCmd.Quit , Access closes the .mdb inquestion then flickers and hangs on a minimum menu screen which cannot be closed?

If there is something else I could look at .dll-wise, let me know, but I'm fairly certain that it is not a version/upgrade issue as I have tried this on all versions/upgrades of Access 2k

by thallone

Ok. I've done some more troubleshooting this morning, and I have narrowed the problem down some. It seems to be a multi-user problem where if the second ( or additional) user stays on after the first user quits, the db cannot close the ldb file and thus the db cannot close.

This discussion is closed to new replies.