[dba-VB] What OS for .Net dev

So use encrypted data in the BE.  You can store as much random rubbish as you want in a 
system table with various embedded nuggets of encrypted information.  Query it on startup.

If the admins touch it at all, your check code won't validate and  the system can trigger an 
alert - then they'll  have to pay for you to fix it. :-)

-- 
Stuart

On 24 Aug 2009 at 17:40, Charlotte Foust wrote:

> We're talking .Net here, Max.  Commercial applications.  We do NOT want
> them to install this on every machine they own, only licensed copies.
> Their mdbs may be SQL Server and their admins have access to the data,
> even though the users can't get there.  It's a little more complicated
> than it sounds.  When the app was in Access, we did something in the
> mdbs.  That is obsolete these days (can you say Citrix?), so we have to
> move with the times.
> 
> Charlotte Foust
> 
> -----Original Message-----
> From: dba-vb-bounces at databaseadvisors.com
> [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
> Sent: Monday, August 24, 2009 4:28 PM
> To: 'Discussion concerning Visual Basic and related programming issues.'
> Subject: Re: [dba-VB] What OS for .Net dev
> 
> As I keep saying, put it in User Defined Properties  in the FE and BE -
> cannot be beaten - travels with the MDB and no way of seeing it.
> Encrypt it too if you want.
> 
> No Registry, no .ini, no visible signs.
> 
> Max
> 
> 
> _______________________________________________
> dba-VB mailing list
> dba-VB at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-vb
> http://www.databaseadvisors.com
>