Versions des environnements
Doug
I just did some more debugging and the problem is definetly in the DYNAZIP restore process. I can manually extract the table from the zip file and I then can use the table. Should have known it wouldn't be on the SDT end. I will try to determine what is happening when the file is getting extracted.
Thanks
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
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement