[AccessD] OT: Network registry?

Gustav Brock gustav at cactus.dk
Fri Jul 23 09:14:05 CDT 2004


Hi Brett

You could ask your app to look for it whenever it launches.
Or you could set a time stamp or version no. in the backend, then let
your app recopy and load the info when it needs the info and an update
is available.

It all depends, of course, on how frequent the info changes.

/gustav


> The info *could* be stored on the workstation.  However, the mechanism
> for updating it is the big question.  How do I keep 70 workstations
> updated when it changes?


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
> Sent: Friday, July 23, 2004 1:36 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] OT: Network registry?


> Hi Brett

> Must the user read the info off the remote file or would it be allowed
> to copy the encrypted info as a file to the users' machines?

> The last option opens for a lot of quite simple solutions like ftp or
> http transfer.

> /gustav


>> Here's the problem.  I have an encrypted piece of information that I 
>> want to share with every computer in my network (~70 machines).  This 
>> information can change at any time so it would be difficult to store 
>> it locally on each workstation.
 
>> Currently I am storing this information in an INI file on a network 
>> share, which causes a series of problems:
>> - I need to hard code the INI file location in the code accessing the 
>> data.  If the file location changes, I would need to update all of the

>> workstations.
>> - All users accessing this file need the appropriate file permissions.
>> There really isn't a single network location that ALL users in this 
>> building access.
 
>> I was thinking of writing a Windows service that could run on one of 
>> the servers, that could monitor incoming requests from client 
>> workstations, and return the encrypted data.  That way, one would only

>> need to know the local IP address of the server, which is unlikely to
> change.
 
>> Any other ideas?

>> Brett Barabash
>> Lead Software Developer
>> Tappe Construction, Co.
>> Eagan, MN




More information about the AccessD mailing list