DBinPhilly
11-20-2009, 02:43 PM
I haven't used SQL Server as a back end to a standard MDB database in about 10 years, so pardon my ignorance.
I have an instance where I plan to write a Microsoft Access Project but in the interim I have imported all the tables from an existing MS Access mdb database into SQL and have linked the SQL tables to a new version of the MDB database - my intent is to avoid going through a number of data conversions. Capture the data on SQL and forget about the old mdb database.
BUT --- I imported the data to the SQL Server. On a workstation I copied all of the objects to a new mdb database. I then linked the SQL Server database using ODBC connectivity. All things worked fine.
But when I copy a version of the new front-end to other workstations, those work stations do not 'see' the SQL tables. I've tried going through the connectivity linking individually but they can't link for some reason.
Why would one work station 'see' the SQL Server and other work stations not see it?
Any suggestions?
I have an instance where I plan to write a Microsoft Access Project but in the interim I have imported all the tables from an existing MS Access mdb database into SQL and have linked the SQL tables to a new version of the MDB database - my intent is to avoid going through a number of data conversions. Capture the data on SQL and forget about the old mdb database.
BUT --- I imported the data to the SQL Server. On a workstation I copied all of the objects to a new mdb database. I then linked the SQL Server database using ODBC connectivity. All things worked fine.
But when I copy a version of the new front-end to other workstations, those work stations do not 'see' the SQL tables. I've tried going through the connectivity linking individually but they can't link for some reason.
Why would one work station 'see' the SQL Server and other work stations not see it?
Any suggestions?