July 3, 2013 at 2:22 pm
Hello,
I am having a problem with an Access application that we use to show and print checks. I believe the application was created with Access 2003 connecting to SQL Server 2005. It ran ok, but not always perfectly, on my old machine (Windows XP) using Access 2007. When we recently upgraded to SQL Server 2008, it continued to run ok. Now we've upgraded from XP to 2007 and I get an 'ODBC -- connection to 'SQL Native ClientDbaseName' failed'.
I can create a new access database and link to the tables that I want to, so I believe that means I have the correct drivers? But maybe the checks database is still connecting with an old string? Although, I can update the tables successfully and still get the error.
I am hoping to not have to rewrite the Access checks program, but if I do - do I use a file source as my .dsn instead of a machine source? It seems like we've had problems getting this program onto other machines, and I'm thinking it might be because it was created with a machine source?
Any articles on recreating ODBC connections when moving to a new system?
Thanks!
Mary
July 3, 2013 at 3:21 pm
Part two to my question: I am trying to recreate the application on the new set up in case this is the only way I can do it (also, it's a learning experience). Each group of check printed has 2 queries that come together in a report to create the checks. The first query is a plain select/wizard query and the second is a pass through. Now I am wondering a couple things:
1. Why use a pass through here? The tables being used are already linked. I don't understand why we would have some queries going to those linked tables and others as pass through?
2. How do I open the pass through without it asking me what to link to every time? Is this done when the report opens?
Thanks!
Mary
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply