Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help with sql connection

Status
Not open for further replies.

ChewDoggie

Programmer
Mar 14, 2005
604
US
Gmorning all,

I could probably make this a shorter question but I thought perhaps that more information might be useful.

I have a "UI" application (contains Forms) that runs on a client's PC. It connects to an .MDF data file locally. The client uses this application to make system-wide changes that are stored in the database. The PC has the database engine installed on it.

I have a second "Service" application (runs as a service) on a separate machine (server). Once a day, this "service" app reads all of the changes made by the "UI" app and sends those changes out to all of the various points. The server does NOT have the database engine installed on it.

These two nodes are functioning properly...SEPARATELY. I now have to test the two together so that they're both pointing to the same data file.

Currently the two use a connection string that looks like this:

Code:
Provider=SQLOLEDB.1;Persist Security Info=False;User ID=ThisUID;Password=ThisPWD;Initial Catalog=DBName;Data Source=LOCALDSN

But of course, I don't think this will work in the installed version b/c this connection string is specific to SQL Server being installed on the local machine.

What will my connection string look like for the "service" app ?

Also, it's POSSIBLE (altho not likely, but still "possible") that the two apps will be connected to the same db at the same time.

TIA

Chew


10% of your life is what happens to you. 90% of your life is how you deal with it.
 
Do you have a system DSN entitled "LOCALDSN" on the "service" server? Even if you don't have SQL installed, you can install the client tools, which include the SQLOLEDB driver.

Now, just for clarification, is the MDF file on a user's machine? I hope not.

-------++NO CARRIER++-------
 
sorry for the delay in replying...

The unfortunate part of all of this is that I don't have knowledge about the machine where the "service" will reside, except that it does not have a SQL engine installed on it.

As a carryover of the previous version of this software, teh MDF file IS on the client's machine.

Thanks!

Chew



10% of your life is what happens to you. 90% of your life is how you deal with it.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top