Linked Table Manager
Thank you for taking the time to report an issue.
What's wrong... Please write below.
On the Tools menu, point to Database Utilities, and then click Linked Table Manager.
In Access 2010 this path is not available. Where can I find this utility
I added a table in the be and now need to link it to the fe. When I launch the Linked Table Manager, it doesn't show up in the list. Am I missing a step?
The 2003 Linked Table Manager had a "Save Password" check box, but it is missing from the 2010 version.
Linked Table Manager doesn't seem to do anything. All tables show as Table: Linked Access except the one new one which just shows as Table
Appreciate any advice.
This doens't make sense to me, and google hasn't been any help so far. Has anyone encountered this or found a way around it
A critical way this operates is by having a mail enabled public folder in exchange. When we create the linked table in the Access Database for one user the linked table pulls in the mail items and we are able to view the items in a form view to carry out actions without issues.
We have a problem though when this database is shared and opened by another user, as the linked table is static to the user it was setup with. A second user receives and error referring to MAPI information not available. I know why this is as when I look at the Linked table manager I see the local path to a temp file on the originals users PC.
Is there a way I can create the linked table to the exchange public folder in a way that allows us to share the database with multiple users? Does the linked table manager have to link through Outlook or can it be done in the back ground with stored credentials
It is one mdb (Unit.mdb) with a linked in table to another mdb (UnitBE.mdb), however if we move the linked in table it will then fail (cannot find .\UnitBE.mdb). However I cannot find out how to amend the linked in table path.
The "Linked in table" manager is greyed out
I was never able to get the tables linked, so eventually the only thing I could see to do was try resplitting the database using the Wizard. After all, This worked really smoothly, except it apparently allowed me to effortlessly wipe out all the data in my backend database. If nothing else, I want to post a warning to others that this thing is a menace.
My next step was to restore my backend from yesterday's backup by copying it over the old corrupted backend, and using the Linked Table Manager to refresh the links. Maybe it wasn't necessary to refresh the links, but my applications seems to be working again.
I still don't know how to add the new table to my backend database. This is another subject not addressed in any of my reference books. And now, the table is missing from the frontend too, though it is still listed as an object. When I try to open it, I get the error message that the Access db engine cannot find the input table.