RE: Triggers - READ

[jlowary@xxxxxxxxxxxxx]

Tom,

At this point they are not, and I wouldn't think they would be in the 
future.  They will be stored in a separate file, with a seq #  replacing 
the data, pointing to encrypted data.  Went this way as the file the CC# 
are stored in is from a Software Vendor and when you encrypt the field 
size of the encrypted data changes to a multiple of 8 (at least for the 
encryption we are using).

There again this was setup by someone else (consultant) and I'm only going 
by what they told me before the project go turned over to me (I could be 
all wet, been there before!).

-- Jim

>Jim:
>
>Just out of curiosity, the "encrypted" field(s) are guaranteed never to 
be key field(s), right?
>
>Tom Liotta