I worked those issue out. It was my misunderstanding of how Cryptor works. Basically there are two ways of registering encrypted files. One is to register one file at a time. The second is to register a file type within a directory. Register c:\temp\*.tmp I open the DBC and read the table names, encrypting each one individually. You must be carefull not to do a blanket register of a file type in a directory where you have registered files individually. That was what was causing my problem.

My problem with Cryptor now is that I have 63 systems installed on lans within a wan. I have a sweeper program to pull data from the lan copies, compile and summarize it. I had to rename the DBC and tables in the summaried app. When you register a file, no other file of the same name can be registed no matter where it is stored. This is only a problem when working with data where table names maybe reused.

I see this as a bug; Cryptor sees this as poor design (in my app).

Cryptor works great is a simple install. In a multi system environment, it leave much to be desired.

Hope this helps.