How do I find the location of a split database's data files in MS Access?

We moved the front end to a different server... and can't find the data. How can I find where it used to be located so that I can import them or link them back to the application?
joelmcmAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dale FyeOwner, Developing Solutions LLCCommented:
generally, if you open the front end in design view, you can mouse over the tables and display the table name and path.  Theoretically, that should tell you were the backend is residing.
Gustav BrockCIOCommented:
Go to design mode of a linked table. Select Properties to see the connection string. That will show where the backend was.

/gustav

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dale FyeOwner, Developing Solutions LLCCommented:
You can also use the connection property to get the connection string of linked tables in the immediate window.

?currentdb.tabledefs("linkedTableName").connect
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

pdebaetsCommented:
I would not recommend importing the tables once you find them. It would be best to continue to have a split database for reasons too numerous to list here.

Once you find where the data is, consider mapping a drive letter to that location (drive Z:, Y:, X: or whatever), then link to the backend through that mapped drive. Some would say that you should map to the server name (such as "\\MyServer\whatever") and this may work well until the server name changes. I prefer to use drive mapping.

For more, see: http://deepintoaccess.blogspot.com/2011/12/map-network-drives-with-vbscript.html
PatHartmanCommented:
You can also open the MSysObjects table to view the connection strings.  Or, just use this query:

SELECT MSysObjects.Database, MSysObjects.Name, MSysObjects.ForeignName, MSysObjects.Type
FROM MSysObjects
WHERE (((MSysObjects.Type)=6));

@pdebaets,
The reason people suggest using UNC notation is because in many organizations, it is difficult to find a common drive letter that is available to ALL users once you get more than about 10 users.  And although servers do sometimes change names, it doesn't happen often.
pdebaetsCommented:
@pat, yes, it can be hard to find a common drive letter and often brings up the organizational issue of standardizing mapped drives which I've implemented at a number of sites. The vbscript example I linked to above comes in handy for these situations.

If such organizational issues can't be resolved, there's a tool I've developed called TableLinker Lite that allows the developer to specify multiple possible locations for the data backend. Linking is attempted for the backends in a list and the first one found is linked to. Details are at: http://www.peterssoftware.com/tll.htm
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.