I'm having a tough time tracking down what is causing the error "Execution of this application has stopped due to a run-time error" when using my database on A2k Runtime.

It seems to be some of the string handling functions that are causing it, i.e., I can add the code :

Dim a as String
a=Space(10)

to a command button in the database causing the problems, and it will crash when the button is pressed.
However making a blank database with a form, a button and the same code, and everything works fine.

Some searching in these forums mentions that it may be due to broken references, but that doesn't explain why the code will crash one database, but not another.
Additionally, how does one chech problematic references on Runtime, as the menu items don't include such things.

Any help at all would be appreciated, and yes, the database works perfectly in my development environment.

Thanks

Richard

I have recently started testing a database using Run Time Access, although I'm using Access 97, this may be an area for you to look at.

Items that worked fine using full A97, brought up compile errors in Run Time. What I did was create a shortcut on the Run Time PC for the database, i.e. target = C:\PROGRAM\Microsoft\RunTim97\MSACCESS.EXE "S:\Databases\whatever.mdb"
and copied this shortcut to the pc with full A97, when I opened this, and compiled the modules, it revealed errors that did not occur in full A97 e.g. I was using the control source name to reference some fields, in the runtime version it would not allow this and had to use the field name.

HTH hope I've explained this well

Just in case anyone else ever has silly, eratic errors with Runtime......

Creating a blank database, and importing everything into it from the problem one can do wonders.