Problems using a2k on XP machines ?

K

Klutzz

I have put together a database using access 2003. I have 2 computers ( my
users ) that are able to open the database using the Access2000 program
installed on thier computers. The problem is that when they close the program
they are not able to open it again unless they have logged out and then back
on to their machines. When this happens I have found that for some reason
"MSACCESS.EXE" is still being shown as an active process in the task mgr.
The database was built using access 2003 but saved in an Access 2000 file
format. If I terminate the process in task mgr. I can then restart the Access
2000 program and open the database as normal, but for obvious reasons I would
preferre not to have my users fiddling around in task manager.
Further, on one of the users computers I installed Access 2003 and did not
have this problem , but due to other issues I had to uninstall 2003 and
reinstall 2000 and bingo the problem has returned. Does anyone have any ideas
what might be causing this ? Or is this possibly a "bug" that I have
discovered.
Any help is appreciated.
Thanx
_klutzz
 
V

Van T. Dinh

There are a few things that can create this behaviour but I am not sure
which version of Access is affected by these. The best way is to avoid
them:

1. Make sure if you create any object in code (Databases, Recordsets, ...),
make sure you close them (if applicable) and then set the Object Variable to
nothing.

2. I think there was a bug using CheckBox value as the criteria for the If
statement. For me, I always use explicit comparison and parentheses to
avoid this. For example, I don't use:

If Me.MyCheckBox Then ...
' (can create problems)

and I do use:

If (Me.MyControl = True) Then ...
' (no problems here)

3. I found in A2K2, using (some?) Calculated Controls in Subforms will
leave a huge footprint (once, I saw 42 MB) in the memory after I quit
Access.
 
Top