[AccessD] relations in which database

Hi Marcel

You didn't mention you have several BEs.
These can not see each other, thus you'll have to maintain referential
integrity via code in your frontend. Relations by themselves won't do
anything other than show you how tables are supposed to relate ...

It will be potentially disastrous to have Excel users to fiddle with
several BEs. To service these, create a new database with queries
linking to the related tables.

/gustav


> And what if I have four BE with different tables that have to be related to
> each other. The only solution is the releationships in the FE? or am i
> missing something. Why do you think it won't work?

> Gr Marcel

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gustav Brock
> Sent: woensdag 4 juni 2003 15:13
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] relations in which database


> Hi Marcel

> The main disadvantage is that it won't work.
> As Charles wrote, relations have to reside in the backend.

> Sometimes relations increase speed.

> If Excel users should access the BE, relations can make this safe. If
> not, create queries they can and must use.

> If you need to adjust relations, open the BE exclusively and perform
> the changes and close.

> /gustav


>> I am stugling with the following. In our current situation I have a FE and
>> a
>> BE database. The relationships are currently stored in the BE database.
>> Now
>> the question is why not put them in the FE database and just leave the
>> plain tables in the be database.

>> Advantages should be
>> - performance in multiuser env.
>> - more control over the database because with each update you can change,
>> add a relationship
>> - peoplo who want to access the database through excel, and so on have
>> more trouble in comprending the database.
>> - field updates, new tables are easily to create instead of using 3rd
>> party backend updaters

>> Are there disadvantages???