Hey Doug

I know it's old but you made it too good. I have never needed to upgrade. It has worked flawlessly since I purchased it. Because of the number of installations involved I don't like to change when things are working great.

Cryptor doesn't work in a datasession. It actually is registered when the application starts and intercepts the I/O as the table is read and written to. It is not being closed or deregistered before I call SDT. The problem I am having is not a consistent one. It doesn't happen all of the time but it does occur. The error occurs in my restore routine. The user has the option of restoring data that was zipped up using DYNAZIP. I only backup the dbf's and fpt's as I figure the cdx can always be recreated. After I restore the dbf's and fpt's I call oMeta.oSDTMgr.reindex("ALL",.f.,.t.). The table obviously has a cdx that was used for a prior version of the table. It has worked flawlessly prior to implementing cryptor. Now, on occassion, the user gets the error "table could not be reindexed - Not a table" in dbcxmgr.ostdmgr.reindexonetable when it tries to open the table exclusively.

I just thought someone who has used cryptor and SDT may have run into the same thing

Tim

>Hi Tim.
>
>>Anyone know of any known issues with SDT 5.1h and Cryptor 5.0.
>
>That's a *really* old version of SDT, although I'm not sure if that's a factor here.
>
>>We just implemented Cryptor and get an error when we rebuild an index on an encrypted table. The error occurs in dbcxmgr.ostdmgr.reindexonetable. It seems the CDX file is erased and the method errors when it tries to use the table exclusively. The error is "table name could not be reindexed - Not a table". Unencrypted tables reindex fine. Any table that is encrypted errors out the same way. The encrypted tables are successfully registered and encrypted with cryptor when the application starts and can be viewed and processed normally except they can't be reindexed.
>
>SDT lives in its own datasession. I'm not sure if Cryptor is datasession-specific or not (I don't think it is), but perhaps Cryptor is being closed or something (which would deregister the tables) before SDT is called.
>
>Doug