G
Guest
I have some accounting and tax receipting type systems developed for
charitable and non profit organization that are exhibitiing strange
behaviour. When the database is being closed, the database password dialogue
box pops up just as it does on system open. This seems to be happening on two
or three system out of about 30 or so who run the apps. For the affected
systems, it is persistent. It's easy enough to click Cancel and the system
completes its close but I have no idea why the password challenge appears at
this point at all nor how to get rid of it..
If a user encounters the problem it happens when they download a new release
of the application that includes new application features - the download
basically replaces their current frontend db. But only a few users who
download a new relaease have encountered the password-on-close problem.
There seems to no common denominator amongst the users with the problem.
One is Win 98 / Access 2000 who runs both the accounting and the receipting
system. Another is Windows XP / Access 2002/XP running only the accounting
system. Another user had Windows XP and Access 2000 but has since upgraded to
Access 2003 - the problem disappered but this was coincident with me
installing a decompiled / recompiled image.
The applications are authored in Access 97 and upgraded to Access 2000 file
format from Access 2002/XP - most users run the Access 2000 version. The
problem seems to be only in the Access 2000 version although it's possbile
some of the Access 97 users have the problem and haven't reported it.
It's hard to debug this problem since none of the machines in the
development envirnoment exhibit the problem in either the Access 97 or Access
2000 verisons - unfortunatley I have limited time to check out the problem on
the few users systems that have it.
The applications themselves are split frontend / backend designs with the
same password used on both mdbs.
I have done a decompile and recompile on the frontend applications on the
development machine and that seemed to clear the problem when downloaded to a
user with a Win XP system. On the Win 98 system the decompiled / recompiled
system didn't clear the problem. So, on the Win 98 system I further tried
unsetting the password on the frontend db. But, when I reset the password
the password-on-close re-appeared. I have not tried decompiling on any
user's machine, so I don't know if that would have cleared it.
I have the sense that there is some problem in my development machine that
is corrupting the application but only selectively for some users. The
development machine is rather old but most of the maintenance patches are
applied (Windows Me, Access 97, and Access 2002/XP SP3, Jet 4 engine SP8) .
If anyone has heard of password-on-close symptoms or has any ideas on a
debugging approach I'd be most appreciative.
TIA
charitable and non profit organization that are exhibitiing strange
behaviour. When the database is being closed, the database password dialogue
box pops up just as it does on system open. This seems to be happening on two
or three system out of about 30 or so who run the apps. For the affected
systems, it is persistent. It's easy enough to click Cancel and the system
completes its close but I have no idea why the password challenge appears at
this point at all nor how to get rid of it..
If a user encounters the problem it happens when they download a new release
of the application that includes new application features - the download
basically replaces their current frontend db. But only a few users who
download a new relaease have encountered the password-on-close problem.
There seems to no common denominator amongst the users with the problem.
One is Win 98 / Access 2000 who runs both the accounting and the receipting
system. Another is Windows XP / Access 2002/XP running only the accounting
system. Another user had Windows XP and Access 2000 but has since upgraded to
Access 2003 - the problem disappered but this was coincident with me
installing a decompiled / recompiled image.
The applications are authored in Access 97 and upgraded to Access 2000 file
format from Access 2002/XP - most users run the Access 2000 version. The
problem seems to be only in the Access 2000 version although it's possbile
some of the Access 97 users have the problem and haven't reported it.
It's hard to debug this problem since none of the machines in the
development envirnoment exhibit the problem in either the Access 97 or Access
2000 verisons - unfortunatley I have limited time to check out the problem on
the few users systems that have it.
The applications themselves are split frontend / backend designs with the
same password used on both mdbs.
I have done a decompile and recompile on the frontend applications on the
development machine and that seemed to clear the problem when downloaded to a
user with a Win XP system. On the Win 98 system the decompiled / recompiled
system didn't clear the problem. So, on the Win 98 system I further tried
unsetting the password on the frontend db. But, when I reset the password
the password-on-close re-appeared. I have not tried decompiling on any
user's machine, so I don't know if that would have cleared it.
I have the sense that there is some problem in my development machine that
is corrupting the application but only selectively for some users. The
development machine is rather old but most of the maintenance patches are
applied (Windows Me, Access 97, and Access 2002/XP SP3, Jet 4 engine SP8) .
If anyone has heard of password-on-close symptoms or has any ideas on a
debugging approach I'd be most appreciative.
TIA