Continuing our AES256 encryption testing, I added a routine to revert back to RC4.
All was good until we starting adding triggers into the mix (no triggers, no 5073 errors).
ADS version in both server (64 bit) and client (32 bit) are 11.1.0.24.
These are the rough steps I do to go back to RC4
+ Open the .add file exclusively via adsConnect101()
+ Remove all triggers from all tables via adsDDRemoveTrigger()
+ Release each table via adsDDRemoveTable()
+ Open each now-free table one by one, calling AdsEnableEncryption() with the corresponding password, then call AdsDecryptTable() in order to remove the encryption and close it.
There were no table structure changes whatsoever; it was going to aes256, then back to rc4.
If I open any freed .adt with hex editor, I can see some metadata in the header area that wasn't there before.
Running our app, doing a search or skipping records usually triggers the 5073 from this point forward.
Unless I restore a backup that wasn't previously encrypted with aes256 or remove the triggers from the .add, the database is pretty much unusable.
I'm aware of the stored procedure sp_SetDDEncryptionType() but for some reason this one fails to properly apply the aes256 encryption, or revert
it back to rc4, and why I had to use the ACEAPI approach instead.
If there's an API function I'm missing (documented or otherwise) I'd appreciate any ideas on this matter.
Thanks!