Obviously PKs and FKs couldn't be encrypted, nor could searchable fields or fields with constraints.. LLBLGen could do the encryption on saves and decrypt the data during a fetch. Encryptable columns could be selected in the designer.

Just a suggestion...

You mean a password field or a textfield? And which kind of encryption do you have in mind?

Otis wrote:

You mean a password field or a textfield? And which kind of encryption do you have in mind?

I don't suppose it matters what kind of field as long as it doesn't interfere with the adapter's fetching routines.

For example, I have a customer who I built a typical forms system for. Even though it's their software, they are not legally allowed to see any of the financial data in the database since it is submitted by THEIR customers. Most of the fields in the database are for financials and they are never used to filter the data on. The filtering is done on the CustomerID or ReportID fields.

ReportEntity report = new ReportEntity();
report.LineA = 23;
adapter.SaveEntity(report, true);

Assert(report == 23);

In the database, 23 would be some illegible string (your choice of encryption type). I could encrypt 23 myself before I assigned it to LineA, but how much fun is that?

I see what you mean. Point is though: if I can do decryption, so can they.