Access JumpStart 2.0 | Blog

A Rapid Development Framework for Microsoft Access

Somehow I keep forgetting this. I keep thinking that at some time in the past I was able to link Database C to the linked tables in Database B which were linked to Database A. Why would this be helpful? My use case would be for my database table separation into different files which I discussed earlier this week. I would be able to transparently reorganize the database across multiple files with the needed tables until I could have all the users relink their main database file.

While that would be convenient, it makes some sense why you couldn’t do it. You’d need to have the same drive mappings as the database you were linking to since Access is actually directly manipulating the file behind the scenes. It would probably be even more of a nightmare than it already is when thinking about how Access has to lock files and records / data pages when multiple users are using the system at the same time.

In any case, now I’m wondering if you can link Database C to SQL Server linked tables in Database B where SQL Server would be Database A. Hmmm… I’m thinking that could cause problems, but I’d have to try it out to see if it works. Anybody out there have experience doing that?