Stuart McLachlan
stuart at lexacorp.com.pg
Sun Aug 16 08:51:24 CDT 2009
Exactly - and if it is in the BE and you have automatic relinking code, you can pick the application up and move it to another machine with no problems. I have never come across a situation where a registry entry is preferable to storing data locally with the application - The same goes for using the AppData path - it just makes it harder to backup or move an application. -- Stuart On 16 Aug 2009 at 14:07, Max Wanadoo wrote: > ...and if that is still considered insecure, you could always write it to > your own defined property in the BE which is completely invisible to the > user. I stick all sorts of license stuff in user-defined-properties in the > BE. You can log people in/out. Count how many concurrent users there are, > what ever you want. > > > > Max > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins > Sent: 16 August 2009 13:33 > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Get Computer Name > > Well, not if the application itself writes the settings to begin with. > > Susan H. > > > > > Yes it came through - but I never use the registry to store settings. It > > > stops the application > > from being portable. > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com