Member Avatar for Pareshja

Hi Guys,

I have completed a vb6 application that uses sql2000 database. I have sql client installed on my pc. I want to install the application on a machine that does not have sql on it. Will it work or do I need to install sql on the clients machine.

Please help.

Kind regards

  • 4 Contributors
  • 4 Replies
  • 108 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Cruize_Invades

Dani AI

Generated

Short answer: you do not have to install the full SQL Server engine on every client if the database stays on a server machine. What each client needs is the appropriate data-access/ODBC drivers and a working network connection to the SQL Server.

: if your SQL Server instance remains on one machine, install the client-side components (MDAC/ADO and the SQL Server ODBC provider that comes with Windows) on the client, or ship them with your installer. As pointed out, the client needs client libraries — but, as suggested, you do NOT need the full SQL Server RDBMS on each client unless the DB must run locally.

Practical checklist to get an ODBC connection working:

  • On the server: enable remote connections (use SQL Server Network Utility for SQL 2000), enable TCP/IP, make sure SQL accepts SQL logins if you use SQL Authentication, and open the SQL port (default 1433) in the server firewall.
  • On the client: create a System DSN via Control Panel -> Administrative Tools -> Data Sources (ODBC) that points to the server name or IP, choose the SQL Server driver, supply credentials, and Test Connection. A DSN-less connection string in your VB6 app avoids having to configure a DSN on every machine.
  • Troubleshooting: ping the server, test TCP connectivity to port 1433 (telnet server 1433), or create a .udl file and double-click it to exercise an ADO connection.

If the app must run against a local database on the client, install a local engine (MSDE for SQL 2000 or SQL Server Express for later versions) and include that in your deployment. For security, do not embed SA credentials in the app; create a least-privilege SQL account or use Windows authentication where possible. As noted, establish and verify the network connection first — that solves most problems.

Recommended Answers

All 4 Replies

Member Avatar for QVeen72

Hi,

"SQL Client" has to be installed on all the Client machine.

Regards
Veena

Member Avatar for choudhuryshouvi

you have to install the sql server 2000 rdbms on the client machine along with your application. it is not possible to run your apps in the machine where sql is not installed as your apps will not access the databases and its associated tables. hope it will help you. but you can install them in any order.

Member Avatar for Pareshja

Thanks guys but first I want to try ODBC connection, because the client dont have to see the sql database or tables. She just needs to see the application

Member Avatar for Cruize_Invades

The application would actually run, but as they said, it cannot access the database and probaby get an error... But if you are trying to access the SQL on using a client.. you should first establish a connection between the CLIENT and the unit where the SQL is installed... then the application would work..

hope it helps.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.