ChewDoggie
Programmer
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:
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.
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.