Hi Eric, I was afraid they would need to install the driver. I'll try innosetup as you suggest
In any case, thank you both, Eric and Vince
Best regards Rafael
El jue, 11 feb 2021 a las 11:17, Eric Selje (Eric@saltydogllc.com) escribió:
Rafael,
They'll have to have the driver installed in order to talk to SQL Server. The best way is to provide them with an Installer program (use InnoSetup - free and easy) that installs your app as well as the driver. It can add a DSN too, although you may want to consider hardcoding that connection string into your EXE so the password isn't visible. Hopefully they're using a SQL account with the minimal privileges needed.
I hope this helps,
Eric
On Thu, Feb 11, 2021 at 6:50 AM Rafael Copquin rafael.copquin@gmail.com wrote:
I have a VFP) app that uses MS sqlserver as backend. The SQL Server is located in a web provider
The connection is achieved by creating a DSN throught the ODBC driver in
my
PC
I need to deploy this app to several clients. But none of them should use their ODBC driver to create the connection, or install the applicable SQL Server Native Client in their PC.
The idea is that I would send them my VFP application exe and they would simply connect to the cloud SQL Server and run the app without any
further
operations to install the exe.
I tried SQLConnect and SQLStringConnect, but they always refer to an existing DSN
Is there a way to accomplish this without my clients intervention other than lodging the exe in the applicable directory in their PC's ??
Please advise and if possible, provide an example on how to do this
TIA
Rafael Copquin
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]