I work on a team building a client server application. Many of the classes are shared, but some only run correctly in the server context. I am looking for a way to add something to these classes, so that we could catch attempts to use them in the client code at compile time.thanks for any suggestions

It's been a while since I encountered this problem. As I remember, there is no solution, other than to switch to using a Java application rather than an applet. The applet runs in the secure "sandbox", and does not have enough authority to get to the database (which would give it the ability to write to a file (the mdb file) on the host machine.