Using the inno setup package software several times, the relevant borlndmm. DLL, CC3260MT. DLL, dbnetlib. DLL, DBNMPNTW. DLL, ntwdblib. DLL packaging, but can't still use the other computer,

CodePudding user response:

As long as an exe file is enough, if consideration is essentially different configuration, can consider the whole a ini file (registry), but this file is not a must, can consider to make it to automatically generate a detected no words

CodePudding user response:

SQL SERVER2008 may need to install SQLLI, this must be installed, but also pay attention to both 32-bit and 64 - bit versions of WINDOWS installation respectively

Your program estimates that most is
this situation
The concrete on the version of Microsoft's official website to find it

CodePudding user response:

If contain MSSQL, also install the MSSQL 2008 service driven, and set to automatic startup mode,

CodePudding user response:

Oh, in addition to the executable file, I really don't have other files, pictures of course resources, the configuration file and directory,
Above said drive I don't know, I used 2008 r2 and 2014 (the Provider=SQLOLEDB. 1) + 10.2 XE + ADO is ok?

CodePudding user response:

By himself on the issue of SQL server driver detection result is: the procedures used in the 2000 driver connection string, in XP and 7 below does not need to install the driver separately, can be normal access server 2000 and 2008

CodePudding user response:

The key to see if operating system under the ODBC driver

CodePudding user response:

You use ADO to connect to the database can build an udl file format, and then call in your application can, afraid of words put this file encryption password leak can completely don't need to add any other things
Unless you use is to streamline the system doesn't even have the basic ODBC driver

CodePudding user response:

You only need to do the client's packaging, server there is to manually install and configure the database, what have I done for many years, not what you say, what the client don't need to pack

CodePudding user response:

There must be a sqlLi 2008 r2

CodePudding user response:

You only need to do the client's packaging, server there is to manually install and configure the database, what have I done for many years, not what you say, what the client don't need to pack

CodePudding user response:

I use DataSnap server to install the MSSQL, client does not need to install,

CodePudding user response:

Suggest to switch to the latest version of the sdac components, can do not need any SQL server driver (including the odbc, oledb, nativeclient, etc.) can access the SQL server, even buy it, also with not a few money, ado this stuff is too old,

CodePudding user response:

Sdac component to use, simple than ado,

CodePudding user response:

Support the SDAC,