Random ideas: Does the module of code have
Option Explicit at the 2nd line from the top of the module? Then it might be worth clicking COMPILE to see if there is something else going on. Is there an error handler in the sub procedure ? What would happen if you GOTO another area of code to try to do the same instructions? with 1. checked to make sure there is no "breakpoint". Did you really do at the menu: Debug..Clear All Break Points? What is the line of code preceding the yellow area? In debug mode, has someone added a WATCH to make the program break? View the watch window to see. http://www.cpearson.com/excel/Debug.htm Could the code work if it ran on another machine?: Is the problem really the code? --- In [email protected], mahonek <[EMAIL PROTECTED]> wrote: > > Hello programmers. I have an Access 2000 program that has been > running fine on winxp pro for the past several years. > > For some reason when the User clicks the button and the program is > ran via an autoexec macro the it stops at the same point in the code > (i.e. yellow highlight on the same line of code), the code window > opens but there is no error message. Once the run/continue button > is clicked it finishes with no problem. > Here are the things I did to try and resolve the problem: > > 1. checked to make sure there is no "breakpoint". > 2. Ran the compact and repair > 3. re-linked/refreshed the links of the linked tables > > Can someone help me identify why this program would keep stopping > like this without providing an error message. Thanks again. > > > Now several months back when we switch from a WINNT4 server to a > WIN2000 server I did copy the original database to this one, re- > named it and re-linked the tables to the new server. But this > program is ran practically everyday and the User says this problem > just started Monday. Thanks again. > > > Mahonek >
