There's a few reasons code stops firing. The 2 things I do most often are...
1. Compact/Repair the mdb.
2. Debug/Compile the code.
I usually create an *.mde file for the users. Another thing you may want to look at for code not firing is to see...
1. Does it happens for all users
2. Does it happen only on 1 computer (regardless of who's logged in)
3. Does it only happen for 1 particular user regardless of the computer (which is often permissions based)
4. Make sure the computer/user has a default printer (as sometimes an incorrect print driver or no default printer can stop code from firing.)
5. Make sure there are no missing references.
You can also run through some of the items here:
Hope this helps in some way. I think though you have to narrow down when it happens and if the problem is user/computer/network based. Unless you're dealing with specialized coding (ie. class modules or non-standard activex controls), versioning is usually not the issue.
Another thing I'll do is create a new mdb file and then import a few forms/objects, test, import other forms/objects, test, etc...etc.. until I can narrow down that it's a specific part of code or module I'm using which causes the problem.
Last edited by pkstormy; 09-17-09 at 18:54.
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)