Linked Table Manaager

[Guest]

Exactly what does the Linked Table Manager do? what updating takes place
when I select the box to "Select tables to be updated" adn what "always
prompt for new location" mean? The tables that appear in the box are the
table names linked to my FE. what am I updating and when would I use this
utility?

Steve

 

[Guest]

Hi Steve,

Exactly what does the Linked Table Manager do?

This utility is used to reset the path of a linked table. If you move a BE
database file to another folder, or rename a table in the BE database, you
will need to either use code to re-link automatically, or use the Linked
Table Manager to re-link manually. In addition, you should delete any
existing links, compact the FE database, and re-create the links from scratch
any time that you make a design change in the BE database (ie. add or delete
a field or an index).

what updating takes place when I select the box to "Select tables to be updated"

The complete path to the BE database, including the name of the table.

...and what "always prompt for new location" mean?

This option will force the display of a File Locate dialog box. Without
checking this option, a link will be refreshed as long as it is a valid path.

The tables that appear in the box are the table names linked to my FE.

I think you meant to say "...linked to my BE". Typically, a FE .mdb file
includes one or more linked tables that point to the BE database. A BE
database typically does not contain any linked tables.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

Thanks Tom, That is exactly what I needed?

Another question: Is it feasable to have the tables in the BE in 2 files.
One file for the tables that I would never (never say never) change and
another file for the tables that will probably change in design as the
application develops. No matter what the user says they always want just a
little more.

I have to ship this ap to several users in different states. the data they
enter in some tables is so geographicaly unique that I could never change the
table after they have entered data for 6 months or so. by having two files
as the backend the control tables (that they never enter data into) could be
changed by me whild not having to worry about their data.

steve

steve

 

[Larry Linson]

It is feasible, but my recall is that you'll have to write/modify code to
handle a two-or-more-file backend. There's some sample code in the Orders
and Solutions sample database, for a single file; you will have to modify it
for more than one. It is linked from
http://support.microsoft.com/kb/208781/en-us.

Larry Linson
Microsoft Access MVP

 

[Guest]

Hi Steve,

Another question: Is it feasable to have the tables in the BE in 2 files.

Yes, but, you cannot use JET to enforce referential integrity (RI) between
tables in different databases. RI is something that you usually always should
enforce. Here is a quote from database design expert Michael Hernandez,
writing on Access' 10 year anniversary:
http://www.microsoft.com/Office/previous/access/10years/hernandez.asp

the data they enter in some tables is so geographicaly unique that I could
never change the table after they have entered data for 6 months or so.

Umm....who just said "never say never"? <smile>

If your database is split into a front-end (FE) and back-end (BE)
application, then you will be able to make design changes to the FE without
having to take users 'off-line'.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

Steve
If you are likely to want to change the back end tables in your client's
databases you might be interested in my BE Update Utility.mdb at :-

http://www.rogersaccesslibrary.com/OtherLibraries.asp#Hibbs,Peter S