Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Program Halt when running Autoexec macro on a WIN XP machine

Status
Not open for further replies.

WYokeCheng

Programmer
Dec 11, 2002
7
US
We are trying to migrate our MS Access 2000 applications (mdb) from OS WIN2000 to WIN XP, but encounter the Halt message when running the Autoexec macro. Strange is that this only happen to one of the applications, the rest were OK.
Anyone can help ?
 
Hi,

You need to work out where it is halting. Does your AutoExec macro run some code or does it just run Macro actions?

I can't remember what the 'Halt' messagebox looks like, but there should be an error message displayed.

Look at the Macro actions in the AutoExec and the error message(s) and post these. It might be easier for someone to help solve your problem.

Dean :)
 
Dean,
Thanks for yr prompt reply.
It was a error message with title 'Action Failed', and body showing following info :
Macro Name : Autoexec
Condition : True
Action Name :RunCode
Argument : Cur_Users
A Halt button on the left. When this button is clicked, a 2nd error message is shown 'Execution of this application has stopped due to a runtime error. The application can't continue and will be shutdown.'

Cur_Users is a form with codes to check for the group that the current user belongs to.

I suspect this has something to do with the security portion.
Note : This mdb file cannot be open using MS Access 2000 program directly, it has to be opened using a shortcut that include the mdw file.
On the users' PCs, we are using Access Runtime to run the
application. It runs fine on Win 2000 but not Win XP. Is there a different version of Access runtime for Win XP ?

 
Hi,

So the error is in the Cur_Users procedure.

You need to enter the database without running the AutoExec Macro (Hold-down shift while opening it up).

Get into VB editor (Alt-F11). Debug Cur_Users by finding this procedure and putting a breakpoint in first line (F9). Once the code enters break mode, step through the code line-by-line (F8) till you find the problem line.

Dean.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top