Mittwoch, 23. Januar 2013 23:40
I have split an Access 2010 database application using the wizard. Upon completion, I renamed the back-end data file and moved it to a new location. The links for all (user) tables have been successfully refreshed using the Linked Table Manager.
However, the front-end application gives an error when trying to view the Application Log. I actually discovered this when trying to view Object Dependencies, which failed because a linked table could not be found... I eventually traced this to the hidden USysApplicationLog table.
The Linked Table Manager does not incorporate this table, and there appears to be no other way to refresh the link. Right now my database is in an inconsistent state because of this broken link.
Donnerstag, 24. Januar 2013 00:06
Okay, I figured out how to relink this table using VBA, so the database is repaired.
However, I am still curious why this table cannot be relinked automatically using the Linked Table Manager? Moving or renaming a back-end database file is a rather common scenario. Is the only solution to write VBA code?
Donnerstag, 24. Januar 2013 05:10I think this table is supposed to be in the FE. If I'm right on that, the Split Wizard was too agressive.
-Tom. Microsoft Access MVP
Donnerstag, 24. Januar 2013 06:25
I think this table is supposed to be in the FE. If I'm right on that, the Split Wizard was too agressive.
-Tom. Microsoft Access MVP
I had thought this as well... but the fact that it was included by the split database wizard caused me to think that somehow this was the way it was intended to work. I had not really considered that Microsoft perhaps had not tested this.
Perhaps someone from the Access product team who might happen upon this thread could let us know if the USysApplicationLog table should remain linked or if it should be restored to a local table?
Donnerstag, 24. Januar 2013 08:30
I'm not sure what that tables does or in which db it should reside. However I think you'd be able to use Linked Table Manager or the Manual User interface to do the linking if you set the back end data base to "show" System Objects and "Hidden Objects". That's a setting in Options / Current Database. By naming the tables Usys that table gets treated as a 'system' table which is hidden by default. Hidden tables do not show in the User Interfaces for linking tables. Hope that helps.
- Als Antwort markiert Gary Voth Freitag, 25. Januar 2013 05:12
Freitag, 25. Januar 2013 05:16
Thanks Ed, I had forgotten about that feature. It's available via the 'Navigation Options' button in the Navigation section of Options->Current Database. This does indeed allow the USysApplicationLog table to become visible in the Linked Table Manager. I had been looking for a similar option in the Navigation Pane's view menu, and I also checked Access Options, but didn't drill down far enough to find what I wanted.