Re: _cipher API vs Qc3Encrypt/Qc3DecryptData vs SQL

[rob@xxxxxxxxx]

A before read trigger would allow us to do things like programmatically 
decide if the person has access to a particular row in a table.  For 
instance, a vendor application often decides who has access to certain 
payroll records based on a number of factors, such as job class, or 
location, or some such thing.  A before read trigger would allow us to 
lock the barn with that same logic instead of just reporting on who stole 
the horse.  Putting a UDF on every field to duplicate that logic, and 
returning a null or default value is not near as nice.  I've done UDF's. 
Check out the faq.midrange.com.

Rob Berendt