[AccessD] Updating SQL Connections

[David Emerson]

Thanks Stuart - that was the better way of doing it that I was looking for 😊

-----Original Message-----
From: AccessD <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com> On Behalf Of Stuart McLachlan
Sent: Monday, 27 December 2021 5:00 pm
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Updating SQL Connections

WHy a seprate file?   Use a usysTable in the FE that stores the connection string and have 
an Autoexec macro that checks the connection so startup. If it's not valid, pop up a form to maintain the data in the usysTable.

On 27 Dec 2021 at 14:31, David Emerson wrote:

> Hi Listers,
> 
> I hope you are having good holidays.
> 
> Has anyone come across the problem where you want to be able to change 
> SQL Connection strings on distributed databases but don´t know what 
> the string is?  Here is the situation:
> 
> A database application is sold to a client.  It has an Access FE and 
> an SQL BE.  I want to be able to link to the SQL BE in code without 
> having to hard code or set up the connection strings before giving the 
> application the client.  The idea is that the connection string 
> information can be stored in a place separate from the actual SQL 
> database, in a place where the client can enter the details, but at 
> the same time is safe from being discovered.
> 
> This excludes saving the connection string information in the SQL 
> Database because the Access FE doesn´t have the connection details to 
> be able to connect to the SQL database to get the connection string 
> details
> 
> One idea is to store the information in a text file (encrypted of
> course) that the Access program can open first and check if the 
> details have been updated.  If not then the Access program asks for 
> the details, saves them to the file, then the file is used to get the 
> connection string details for connecting the Access FE to the SQL 
> backend.
> 
> Can anyone think of a better way of doing this, or any problems with 
> this approach?
> 
> Regards
> 
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
> 
> 
> 
> 
> 
> 
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com


-- 
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com