Split DB Questions

W

webunit

I'm new to using a split database and I have a few basic questions:

It may sound dumb, but is it always necessary to have the front-end
connected to the back-end? Sometimes I'm only interested in modifying code
or forms and would prefer not to make a connection to the back-end on the
server.

Also, is there a quick way to connect a front-end to a different back-end?
The Linked Table manager is painfully slow since it appears that you have to
relink each table one at a time (even after choosing Select All). Is there a
faster way?

Thanks,
Webunit
 
N

NetworkTrade

when the FE opens it is always linked....there is no reason/benefit to unlink

the Linked Table Manager has a select all - - one does not relink 1 table at
a time.

your fears are unfounded.... split db is the norm and very robust...
 
W

webunit

First, on the splitting issue. No worries, the database is already split so
I'm sold on the idea.

But when I use Select All and Always Prompt for New Location in the Linked
Table manager, it prompts me for each and every table individually AND it
makes me navigate to the back-end over and over. (Access 2007 under Windows
XP). If I don't select the Always Prompt... it just refreshes the links. I
want to give it the new back-end once.

What am I doing wrong?

Thanks,
Webunit
 
B

Beetle

I keep a copy of the BE on my local hard drive. Not all the data, just the
tables and some example data. I have a master copy of the FE which is
linked to this local BE. When making design changes it is much faster and
you don't have to worry about corrupting any real data.

When the design changes are done, make a copy of the updated FE
and re-link it to the BE on the server. When you use the linked table
manager, make sure you select "Always prompt for a new location"
 
J

Jeff Boyce

If you are working with a back-end located on a Local Area Network server,
you need not concern yourself with "making a connection". On the other
hand, if you are modifying forms, queries, reports, code, etc. in a copy of
the front-end (on your PC), it might make sense to re-link to a TEST
back-end, rather than stay connected to the PRODUCTION data.

The Linked Table manager provides a relatively painless way for you to
connect to the TEST data (and back again). If this is too painful, you can
spend considerable time learning how to write use the code that
automatically re-links to whatever back-end you specify. You can find
samples of this by searching on-line for "re-link", but you'll need to
customize it for your situation.

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
W

webunit

OK. I like this idea. I do a lot of coding anyway. I will check out sample
code online. I realize that code development can take longer than just using
a manual method (for infrequent tasks) but I usually learn a lot by coding
anyway.

Thanks.
 
N

NetworkTrade

if LinkTableManager is prompting for individual tables, despite the SelectAll
- - there is something wrong.

I have experienced this and so I understand what you are saying; but it is
definitely not what is suppose to occur.

If feasible; try simply delete all linked tables completely; and then
relink to them using the Get External Data... and see if from there the
SelectAll works ok going forward....
 
S

SteveD

The Link tabe manager works well with select all only when the tables
selected are from the same source location. If you have two back-end data
sources, then select all of the table from a single source and link, then do
the other source.

SteveD
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top