Home/ Questions/Q 8570587
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T18:35:34+00:00

This isn’t so much a programming issue, but i’m not sure where else to

  • 0

This isn’t so much a programming issue, but i’m not sure where else to get this level of expertise.

In any case, the issue i’m having is getting a legacy application to run locally on my machine. it connects to a SQL server using this connection string 

Provider=SQLOLEDB.1;Persist Security Info=False;User ID=UN;password=PW;Initial Catalog=DB;Data Source=IP

(where of course UN, PW, DB and IP are different, real, values)

I’ve changed it to this, to connect to a SQL Server Express instance on my local box: 

Data Source=MY-PC-NAME\SQLEXPRESS;Initial Catalog=DB;Integrated Security=True

The app errors out with a generic cannot connect type error, which isn’t helpful in the least bit.

Anyone have any advice? I don’t have much more information on this blasted program ..

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This eventually worked Provider=SQLOLEDB.1;Persist Security Info=False;User ID=;password=;Initial Catalog=;Data Source=mypcname\SQLEXPRESS;Integrated Security=SSPI

    I have no idea why. I needed to specify the integrated security.

    Thanks for your help!

    • 0