Linked Tables Issue, connection string, default db

[Scott]

Have you ever typed up a question to the group, only to figure out the
answer as you typed it out?

In case it helps someone in the future, I'm thought I would explain it
here.

I had been asked to improve an mdb file. The upsizing wizard wouldn't
convert it to a project, so I opted to move the tables to a SQL server.
This all seemed to work well, with the linked tables working perfectly
for the testers in this department.

Several of the end users, however, were getting an odd error. The
linked tables would not connect. The same DSN-less connection string
worked perfectly for many users, but didn't work at all for others.

Here are the connection strings:

****Current... worked for people in my department and others*****
Description=ProdTrusted;DRIVER=SQL
Server;SERVER=CRRRSQL01;APP=Microsoft Office
2003;WSID=CRP000;Trusted_Connection=Yes

****Test version... created on a user's computer, allows him access****
Description=test;DRIVER=SQL Server;SERVER=CRRRSQL01;APP=Microsoft
Office 2003;WSID=CRM01000;DATABASE=S0200;Trusted_Connection=Yes

As I entered these strings here, I realized that the test version had a
database specified. This is because the user's computers were
defaulting to a different db on the sql server. The folks in this
department were defaulting to S0200... but other users were defaulting
to another db. Once I added the DATABASE=S0200, it worked fine.

(One final note... the connection strings are changed, in case you
wondered if I was being silly to put them on a newsgroup. I realized
the problem while I was changing the strings before posting them.)

I hope this helps someone in the future!

 

[Smartin]

Have you ever typed up a question to the group, only to figure out the
answer as you typed it out?

In case it helps someone in the future, I'm thought I would explain it
here.

I had been asked to improve an mdb file. The upsizing wizard wouldn't
convert it to a project, so I opted to move the tables to a SQL server.
This all seemed to work well, with the linked tables working perfectly
for the testers in this department.

Several of the end users, however, were getting an odd error. The
linked tables would not connect. The same DSN-less connection string
worked perfectly for many users, but didn't work at all for others.

Here are the connection strings:

****Current... worked for people in my department and others*****
Description=ProdTrusted;DRIVER=SQL
Server;SERVER=CRRRSQL01;APP=Microsoft Office
2003;WSID=CRP000;Trusted_Connection=Yes

****Test version... created on a user's computer, allows him access****
Description=test;DRIVER=SQL Server;SERVER=CRRRSQL01;APP=Microsoft
Office 2003;WSID=CRM01000;DATABASE=S0200;Trusted_Connection=Yes

As I entered these strings here, I realized that the test version had a
database specified. This is because the user's computers were
defaulting to a different db on the sql server. The folks in this
department were defaulting to S0200... but other users were defaulting
to another db. Once I added the DATABASE=S0200, it worked fine.

(One final note... the connection strings are changed, in case you
wondered if I was being silly to put them on a newsgroup. I realized
the problem while I was changing the strings before posting them.)

I hope this helps someone in the future!

Good Job Scott!

I have started many messages as new questions, only to find as I type
the answer reveals itself.

It doesn't always work, but sometimes thinking critically about the
dilemma puts us in a new mindset.

Yet another benefit of Usenet (^:

 

[David F Cox]

It is what I call the "cardboard consultant" syndrome. You have this
imaginary cardboard figure to which you explain very carefully how you
have tried everything except ..
or it couldn't possibly be this because ....

Worth their weight in gold the old CC.

 

[Smartin]

It is what I call the "cardboard consultant" syndrome. You have this
imaginary cardboard figure to which you explain very carefully how you
have tried everything except ..
or it couldn't possibly be this because ....

Worth their weight in gold the old CC.

I couldn't have said it better.

Glad to know you're about (^: