keeping user out of visual basic

[dreamspy]

Is there any way of disableing users from entering visual basic from access?

I have occasional problems with visual basic popping up on my clients computers, f.x. when there is a code error, the debugger starts up.

 

[Greyowlsl]

Just make your database flawless so the code window doesent have to open.

 

[KernelK]

Use an .MDE File

You can compile all of your code, and convert your .mdb to an .mde which contains no source code. If the application runs into an error, it will probly terminate itself unless you define your own error handling routines however, the code will not be displayed from this file ever again.

 

[nikkypickles]

Probably not best practise but...

Why not put Error Handlers in your code that open a simple message box saying "Error" (or similar - try a search on suggested error handler messages). Since you can specify that your message box only has an OK button, they can't open the debug bit.

Although compiling and making it an MDE is probably the best route - it's not something that's feasible for me because of the dynamic nature of the work - so I've been looking at alternatives.

 

[ghudson]

All of your subs and functions should have an error handler! Do not use macros for you can not use any type of error handling in a macro.

You can password protect the VBA modules.