|
Ok. Got it working. Had to change from: CREATE TABLE ROB/TESTAC3 (MYKEY BIGINT NOT NULL WITH DEFAULT, SSN VARCHAR (50) NOT NULL WITH DEFAULT) to CREATE TABLE ROB/TESTAC3 (MYKEY BIGINT NOT NULL WITH DEFAULT, SSN VARCHAR (50) NOT NULL WITH DEFAULT for bit data) insert into rob/testac3 values(1, encrypt_rc2('123-45-6789')) 1 rows inserted in TESTAC3 in ROB. select mykey, decrypt_char(ssn) from rob/testac3 ....+....1....+....2....+....3....+....4 MYKEY DECRYPT_CHAR 1 123-45-6789 ******** End of data ******** Extremely easy. Talked to database support. They would like the design changed so that the insert would fail if you didn't have "for bit data" turned on. But apparently the "cones of silence" won over. Can your programmers handle that? Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.