Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1256
  • Last Modified:

Convert Access Linked table location from mapped Drive to ODBC

I have an Access database which is split into a back end and front end.  The front end contains linked tables which have been linked to tables in the back end using a mapped drive path to the location of the backend database.  I have upsized the backend database to SQL server 2000 and would like to change the location of the linked tables in the front end so they are linked via an ODBC connection.  However I don't see any way of doing this in the linked table manager.  Does anyony know if this is possible without having to delete the tables and relink them.  The Front end is very complex and I don't want to have to recreate all the relationships, queries etc.
0
DCMBS
Asked:
DCMBS
  • 3
1 Solution
 
adraughnCommented:
You need to relink them. Moving from access to sql is a major change. Even though you have migrated the tables, things have changed. Data types are different. Connections are different. Take the time to do it right and avoid issues going forward.

post back if you need more help with your migration.

-a
0
 
adraughnCommented:
please read the tips on this thread for migrating from Access to SQL, they may help.

http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SQL-Server-2005/Q_22517413.html
0
 
DCMBSAuthor Commented:
I thought that was the case but I am ever the optimist.  The client is complaining about poor performance, which I believe is because of the way the tables are linked and I wanted to try a quick mod to see if using an ODBC connection would improve the performance.  A major reworking of the database is not something I can undertake at present so I think this will have to wait.
0
 
adraughnCommented:
Note that you will see poor performance at first when migrating your tables from access to sql. sql can improve performance, but it takes some work. you would need to rewrite your queries as views and stored procedures so that the work is done on the server. once you change those, you will see an improvement in performance.

It does take time, but you may want to consider it as a future project. The other great things about moving backend to sql is that you can take advantage of sql server reproting services, web reporting.... it's very nice. users love it, and it's easy to use.

post back if you need help. the majority of the access experts have felt the pains of migrating a backend to sql. we can help.

-adria
0

Featured Post

[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now