[AccessD] relations in which database

Hi Marcel

> Hi Charles,

> The advantages are not mine but I got them from several forums.

Oops! I would consider signing off from such forums.

> We have
> noticed that the performance of our application is slowing down. In our
> search to solutions we have found some usefull things. 
> One of the solutions is moving the relationships from the be to the fe. The
> jet engine can do it joining, selecting and interpreting localy in it own
> database instead of over the network in another (BE) database. So only
> storage is in the BE all the intelligence is in the FE

> In mine humble opinion this sounds logical and in situations when you have
> more than one BE I think this is the only solution to relate tables to each
> other. So why not do this, it seems to work and available in Access. Am I
> not sure how JET acts when there are the same relationships in the FE and BE

You'll have to read up on this. One hint: you can choose to access one
BE only. Doing so doesn't leave neither Access nor Jet a chance to
know what's going on in another BE, not to say "synchronize" these
behind the scene.

/gustav