Database will not open

[Mitch_77]

I have an Access 2002 database that will not open under a local account on a
user's laptop. This same database opens and runs fine if the user logs in
with their domain account. Their local account has access to all network
drives and folders needed for this database to run but it stops and gives an
Action Failed error when it runs the first macro. This macro is an update
check to see if a new version is available. I have removed this macro and
set the database to open the Password form at start-up but it gives a
run-time error when they submit their password. This user has about a dozen
other databases installed on this local account and they all work fine with
this same update check macro running at startup.

I have run the same copy of this database on other machines using domain
accounts and it runs fine. I have removed and re-installed Runtime with no
luck. I have reset the users network and local passwords and made certain
they have access to all network resources but I still get the error message.

The laptop is running Windows XP Pro with MS Office 2007 and Office 2002
Runtime for the databases.

Any help would be greatly appreciated.

Thanks in advance.

 

[Hans Up]

I have an Access 2002 database that will not open under a local account on a
user's laptop. This same database opens and runs fine if the user logs in
with their domain account. Their local account has access to all network
drives and folders needed for this database to run but it stops and gives an
Action Failed error when it runs the first macro. This macro is an update
check to see if a new version is available. I have removed this macro and
set the database to open the Password form at start-up but it gives a
run-time error when they submit their password.

Can you capture the run-time error and tell us what it says?

Other than that, I don't see any way to help you. I would have
suspected differences in Windows permissions between the local and
domain accounts ... but it sounds like you covered your bases on that
score already.

 

[Mitch_77]

Can you capture the run-time error and tell us what it says?

Other than that, I don't see any way to help you. I would have
suspected differences in Windows permissions between the local and
domain accounts ... but it sounds like you covered your bases on that
score already.

The second error states: "Execution of this application has stopped due to
a run-time error. The application can't continue and will be shut down."
The database closes when the OK button is clicked.

 

[Hans Up]

The second error states: "Execution of this application has stopped due to
a run-time error. The application can't continue and will be shut down."
The database closes when the OK button is clicked.

I think that's the run-time's generic "last-ditch" response to the
unhandled error within your application.

In order to find out anything useful about the error, you will have to
set up error-handling within your application (On Error GoTo <label>).
Then your error-handler code must report err.Number and err.Description
in a MsgBox or by writing to an external log file.