This action will reset the current code in break mode.

[mous]

Do you want to stop the running code?

Yes - No

This is an error message we are experiencing more and more on Access 2000 since migrating from 97.

The above happened on this occasion with a simply filter on a table - on one column and then using the scroll buttons to view another column.

Should there be code running on a table. Not that I have programmed!?!

Any ideas.

Thanks

 

[Mile-O]

That's not an error message - that's a question.

If your database falls down somewhere it'll show you the line of code (provided you have no error handling routines) where the error occurs.

That question is appearing because you are trying to change code while the database is still running.

 

[mous]

Where should I look for this code? It not something I've done and it doesn't give me the option to view it either unless there is some other way I don't know about.

If I click Yes nothing happens if I click No again nothing happens. The only way out is to do CTRL+ALT+DEL.

Maybe I should have mentioned this before - sorry.

Thanks

 

[Fizzio]

Check your startup routines.
Do you have a macro called Autoexec ?
Does a form load on the opening of the Db and if so, what VBA code does this have associated with it? (go to design mode for that form then click on the code button to see all the code associated with it.)

Open the Db with the startup routines disabled by holding [Shift] whilst you open the Db and see if you get the same message.

 

[mous]

The databases (it happens on more than one) have no start up and no autoexec.

The databases are for interogation purposes only not for distribution so there's no fancy forms, reports, startup etc.

Just now, we have another : when in a table and selecting the Filter For ... from the right-click mouse menu on occasions does nothing when text is typed in and the filter actually takes place.

Have we installed Access with some sort of configuration that is incorrect or are the tables we are looking at i.e. ODBC connections to a SQL database inherited these anomlises.

Thanks