>Fred,
> Sorry I skipped that part of the statement. "If I encrypt/decrypt the files..."
>
>IOW, I encrypt the files for distribution, then decrypt and open them. The table is now open and readable, but since it doesn't have a physical file reference, the SELECT SQL will fail (the physical file is encrypted).
>
>My data is proprietary, I don't want to expose the tables as dbf files to the end users. I want to limit access to the data via my application.
>
>I DO open them "NOUP" already.
>
>>If the data is encrypted, nothing in VFP wil lbe able to deal with it until they are decrypted.
>>
>>Maybe you can just distribute the tables separately, marked as read/only and open them with USE table NOUPDATE?

I don't se how you can encrypt decrypt the files if you've got them as part of your .EXE (or any other .APP). The fact that you've done something to decrypt the file *must have* made some sort of new file out of it.