J
@Sgt. Zim said:@Albatross said:Lock the VBA code down with a password: Tools > Project Properties > Protection (Tab).
Only give the password to "real" programmers.
The way I read this, he needs to give access to "programmers," but they're all of the sort that write code that shows up here ...<flame-retardant underwear mode="on">This falls into the "right tool for the job" realm. I'm presuming that since you're using Access '97, there's a logical reason, and any of the "use a better tool" comments are pointless... The job is to drive screws, so try to make the best of that screwdriver; don't reach for a hammer.Were I in your (hugely uncomfortable) shoes, I'd probably take all of the things that I don't want getting misused, and wrap 'em in a VB6 DLL. The differences between VBA and VB6 aren't huge ... Of course, that might be a WTF in its own right. It's a bit more difficult from the "VBA programmer's" perspective to call a DLL than to use the code modules in the MDB, but it would at least prevent the script-kiddies from deleting random bits of code, and you could easily leave your date check in place.Or do they need to actually change parts of it? If that's the case, your best bet is to scrub all references to yourself from the code, and hope that it never comes back to haunt you. Of course, you'll still know, but at least no one else will.<flame-retardant underwear />Good luck.
You can easily fix the "difficulty in calling a dll" by distributing a wrapper module. However, if he builds a COM dll in VB6, it is very easy to call it from VBA. So easy that building a wrapper module would seem silly.