Protecting VBA Code

[hansdbase]

Are there any near foolproof ways to protect the vba code in access from being accessed and viewed by a user? If I compile the file will users still be able to see the code if there is an error the execution of a subroutine? Thanks.

[Minty]

If you compile and save the file as an ACCDE then the code is unreadable and inaccessible, without getting someone to pay to have it reverse engineered.

[hansdbase]

Minty, Thank you. Is there anything else technically I can do to prevent it from being reverse engineered? And if I compile it as you suggested, will the code still be hidden even if a subroutine results in an error? In other words will a "debug" option present itself to the user? Thank you again.

[Minty]

Once it's compiled as a Accde, there is no debug option.
The database will simply crash out if you haven't got decent error handling coded in.

As far as reverse engineering it, it's a complicated and expensive process, and most of the firms that provide it as a service require some form of proof of ownership before undertaking the work.
As with all things if someone is prepared to put a lot of effort / time / expense in you won't beat them, but how desperate are they?
Your code will be as protected as it can be in an Access environment.

Obviously, you must make sure you have a normal accdb version backed up and saved for your own development purposes, otherwise you're into paying someone...