Client Database Solution, or best practice
From: Elric (LordElric_at_qwest.net)
Date: 04/22/04
- Next message: Bnaya Eshet: "Missing Feature in ADO.NET 2.0"
- Previous message: Al Reid: "Re: ADO reads null values from Sybase stored procedure result"
- Next in thread: Cor Ligthert: "Re: Client Database Solution, or best practice"
- Reply: Cor Ligthert: "Re: Client Database Solution, or best practice"
- Reply: Val Mazur: "Re: Client Database Solution, or best practice"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 22 Apr 2004 15:21:04 -0700
I'm currently working on a client application in .net, written in C# (VS 2003). I'd like feedback on a "best fit" for a local client database to store data. Not a whole lot of data, but enough to require a solid solutions that is secure and preferably encrypted.
I've considered access or even the SQL desktop engine. Does anyone have suggestions, personal experiences, or general best practices on storing local data in a secure fashion? I'm just not seeing a lot of answers from MS on this.
Thanks!
Elric
- Next message: Bnaya Eshet: "Missing Feature in ADO.NET 2.0"
- Previous message: Al Reid: "Re: ADO reads null values from Sybase stored procedure result"
- Next in thread: Cor Ligthert: "Re: Client Database Solution, or best practice"
- Reply: Cor Ligthert: "Re: Client Database Solution, or best practice"
- Reply: Val Mazur: "Re: Client Database Solution, or best practice"
- Messages sorted by: [ date ] [ thread ]