Linked Table Manager

[Clois Beckwith]

I just installed Office 2003 Professional at home with SP2. Brought home a
Backend Database and the Frontend database files. Put them in my documents
folder, created a shortcut on the desktop and it opens the front end, like it
should; however, when I click on the Linked Table Manager. it pops the
backend tables. I select all and then click the prompt for new location and
hit OK. Normally, you select the first file where the backend is and it
automatically links all the subsequent files (Tables) back to the Frontend.
It won't do this....if I select 3 or 4 tables as they popup and link to the
backend. They do NOT link to the local address. They are still showing my
server address at work. I don't have this problem at work, they link
properly. Any ideas?

 

[Arvin Meyer [MVP]]

Usually when this happens, there is 1 or more tables which source a
different database. So then the linked table manager will ask for each
table, 1 at a time. You can alleviate this by either finding and deselecting
the table(s) which don't match, then doing them separately. Alternatively,
you can delete all the links and use: File >>> Get External Data >>> Link to
reestablish the proper connections.

 

[Clois Beckwith]

Here is what I discovered at work:
1. when I setup the permissions for all the tables on the mdw file, I did
NOT remove the Admin, so that the permissions for the group where the only
permissions available to the users. It left a back door in, for someone with
a little knowledge to go in an change permissions.

2. After I logged in as an Admin, I was able to give myself the
permissions to administer the tables. Then I changed to the mdw file for the
orignal database after I deleted the tables I did not need. Then I deleted
the links on the frontend and then Linked back to the backend tables. Now all
the links on the tables are as they are suppose to be. Thank God....

3. Now when I run the Linked table manager, it runs automatically on a
local copy relink. This problem is resolved.

good information, this helped.

 

[Arvin Meyer [MVP]]

You can't remove the admin, but you can remove his permissions (which you
should do) Create new user with admin rights and make him the owner of all
the objects. It is important that you follow the guidelines in the security
FAQ if you want a secure database. Here's everything you need to know:

Security FAQ
http://support.microsoft.com/download/support/mslfiles/SECFAQ.EXE

Lynn Trapp's summarization:
http://www.ltcomputerdesigns.com/The10Steps.htm

KB articles:
http://support.microsoft.com/default.aspx?scid=KB;en-us;q165009
http://download.microsoft.com/download/access97/faq1/1/win98/en-us/secfaq.exe
http://support.microsoft.com/default.aspx?kbid=325261

Joan Wild's articles:
http://www.jmwild.com/security02.htm
http://www.jmwild.com/security97.htm
http://www.jmwild.com/SecureNoLogin.htm
http://www.jmwild.com/Unsecure.htm
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com