[AccessD] Read External File for Path String

I have run into that problem here at work.  That is why I went back to ini
files and have also played with XML files.  Proved to be easier (using an
ini file) than trying to fight an uphill battle to get the workstation
image for 60 of the 350 plus users for one of my apps changed.

Jeffrey F. Demulling
Project Manager
U.S. Bank Corporate Trust Services
60 Livingston Avenue
EP-MN-WS3C
St. Paul, MN  55107-2292
Ph: 651-495-3925
Fax: 651-495-8103
email: jeffrey.demulling at usbank.com


                                                                           
             "Charlotte Foust"                                             
             <cfoust at infostats                                             
             ystems.com>                                                To 
             Sent by:                  "Access Developers discussion and   
             accessd-bounces at d         problem solving"                    
             atabaseadvisors.c         <accessd at databaseadvisors.com>      
             om                                                         cc 
                                                                           
                                                                   Subject 
             01/19/2006 10:08          Re: [AccessD] Read External File    
             AM                        for Path String                     
                                                                           
                                                                           
             Please respond to                                             
                  "Access                                                  
                Developers                                                 
              discussion and                                               
             problem solving"                                              
             <accessd at database                                             
               advisors.com>                                               
                                                                           
                                                                           




That works if you have permission to write to the registry, Gustav.
We're running into more and more situations where the user does  NOT
have permission to read and write the registry.  Apparently the "new"
approach is to use an xml file in documents and settings.

Charlotte Foust


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Thursday, January 19, 2006 2:10 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Read External File for Path String


Hi Dan

Or use the registry. This is what it is for.
Susan just wrote an article on this (hidden somewhere for the public, I
guess) but it's quite easy if you use:

SaveSetting(..) and GetSetting(..)

/gustav

>>> dwaters at usinternet.com 19-01-2006 01:37:53 >>>
Hello Everyone,

I just spent half the day struggling with the movement of a system from
one server to another.  The server path is hardcoded in one place in a
startup form.  What would have helped me a lot is to have the path in a
text file or ini file external to the database and stored in the same
folder.

Security is not an issue here, just my convenience, as my plans for the
day were pretty much blown up!

Using a file for information like this sounds like it might be a fairly
typical solution.  Does anyone do this or something like it?

Thanks!
Dan Waters


--
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




------------------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation.
==============================================================================