Access 2000 remebers breakpoints

[seaport]

I've run into this problem several times. I worked on my testing database, setting breakpoints and fixing all bugs. Then I compacted the database, copied the database into the production computer, and relinked that database with backend databases. Everything works fine.

However, the front-end database somehow remembered breakpoints, and users got freaked out when they got into the debug mode, looking at those VB code. Certainly, this situation did not occur when the database was mde file.

Did anyone have the same experience?

Thanks.

Seaport

 

[PHV]

Before compacting the database, put a breakpoint anywhere in the code, then get rid of all (Ctrl+Shift+F9) and finally compile the database.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[RoyVidar]

Yeah - even sometimes stops at lines where an error, but no breakpoint was.

Try:
* do a little change in code (hit enter/backspace)
* remove all breakbpoints
* debug | compile and save

Roy-Vidar

 

[seaport]

Actually, what I did to fix the problem was to cut the line of code where VBA stoped, save, paste the line of code back, save, then compile and compact the database.

It worked. But I still have not clue why this happened.

PHV and Roy,
Your reponses implied that I have to remove all breakpoints before I close the database.
I always think that closing a database will automatically remove all breakpoints, is this true?

Seaport