Thank you, this is one way of doing it, I thought where would be a easier
way.

Do you mean that the decryption should be done in the OnCalculateField?

Regards
Olafur
-----Original Message-----
From: Helen Borrie [mailto:helebor@...]
Sent: 26. februar 2003 11:07
To: IBObjects@yahoogroups.com
Subject: Re: [IBO] Encryption of data


At 10:53 AM 26/02/2003 +0000, you wrote:

>Hi Helen, do you have a suggestion on this?
>
>I'm going to implement encryption of my data so that it will not be

readable

>to the sysdba on database level.
>
>I'm using TIB_Transaction, TIB_Datasource, TIB_Query and a TIB_RichEdit
>control.
>
>I would like to do the encryp. in my app so it will be sent encry. to the
>server.
>
>Where / in what event do I encrypt the data and where do I decrypt back

the

>data before it will show in the RichEdit control ?
>
>Can you help me with that?

From own experience? no. I haven't done it.

But I assume you will need to do something along these lines: map
calculated fields for each of your encrypted data fields and hide the data
fields. AFAIK, the encryption routine should take place in the
OnCalculateField event (which needs to refer to the Row object);
duplicate
the decrypted data into non-data-aware fields for editing; provide
parameterised xxxxSQL statements for all DML operations, calling SPs to
perform the ops; and perform the encryption in BeforePost by encrypting
the values from the non-data-aware controls into the params of stored
procedures.

Helen



Yahoo! Groups Sponsor
ADVERTISEMENT





___________________________________________________________________________
IB Objects - direct, complete, custom connectivity to Firebird or
InterBase
without the need for BDE, ODBC or any other layer.

___________________________________________________________________________
http://www.ibobjects.com - your IBO community resource for Tech Info
papers,
keyword-searchable FAQ, community code contributions and more !

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


[Non-text portions of this message have been removed]