Access Runtime and ODBC connection can't get it to work..

[moto485]

Hey guys I have a Access front end connected to a MS SQL database using a ODBC connection which is working fine of course.

When I compile it as a runtime version and install it on the business computer I get an error with the ODBC connection (sorry I can't remember exactly what pops up). On the business computer I have installed SQL Native Client and in the ODBC added a System DSN (which works).

How do you guys go about this? any tips? is there something I should be doing when saving as runtime?

Thanks for any help

 

[GinaWhipp]

Why are you using the Native Client? Just use the SQL Server... at the bottom of the list.

 

[boblarson]

Why are you using the Native Client? Just use the SQL Server... at the bottom of the list.

Gina - depending on which version of SQL Server and which operating system the client is on, it can necessitate the use of the SQL Native Client or SQL Native Client 10.

 

[boblarson]

When I compile it as a runtime version and install it on the business computer I get an error with the ODBC connection (sorry I can't remember exactly what pops up).

Then go find out. The messages are important as we can't see what you see and without giving us the message it is like going to the doctor and saying, "Doc, I have an extreme pain, what's wrong?"

 

[GinaWhipp]

@Bob,

Yes, I do know that but since no information was provided as to versions, I was hoping it would open a dialog. I guess it kinda did, with you!

 

[moto485]

I will find out exactly what the message said but I'll have to get back to you on Monday when I'm there. Yea had to use native to connect to this database. I was hoping it was hoping someone would just go "hey you forgot to do this!" but that's okay I'll be back with some more info.

 

[vbaInet]

The chances are that you shouldn't be using the Client in your production environment. Client is mostly when you have a local SQL Server installation running it as localhost.

 

[boblarson]

The chances are that you shouldn't be using the Client in your production environment. Client is mostly when you have a local SQL Server installation running it as localhost.

No, sorry that is completely incorrect. Since it seems I'm going to have to type it out for everyone - here you go:

 

[boblarson]

And this is information I had received from Mary Chipman, former MVP, who went to work for Microsoft on the SQL Server Team.

In a lot of instances you can still use the SQL Server generic driver. But if your database uses any new features of that version, then you need to follow the matrix.

 

[vbaInet]

That's why I said mostly and italicised it too... well at least that's what I've seen it used for in some prod envs. I'm not a SQL Server person anyway, so you must be right.

 

[vbaInet]

No, sorry that is completely incorrect. Since it seems I'm going to have to type it out for everyone - here you go:

And I've taken a copy of the table for reference. You didn't quite type it out though Bob

 

[boblarson]

And I've taken a copy of the table for reference. You didn't quite type it out though Bob

Actually I did. I typed the first part of my post and then went into Microsoft Excel and typed it out (it was going to be easier to use a matrix and it isn't all that easy just typing it here). So then I took a screen shot of it using SnagIt! and uploaded the pic to my website and then referred to it. (I did that so I hopefully can just reference it again, which I'm sure I'll have to do.)

 

[vbaInet]

Actually I did. I typed the first part of my post and then went into Microsoft Excel and typed it out (it was going to be easier to use a matrix and it isn't all that easy just typing it here). So then I took a screen shot of it using SnagIt! and uploaded the pic to my website and then referred to it. (I did that so I hopefully can just reference it again, which I'm sure I'll have to do.)

And you made me type it all out again haha.