[AccessD] relations in which database

In a split Access FE/BE world, the Access BE is nothing but a container of
tables.  You can keep a copy of the relationships in the BE for reference
but in order for the FE to do its job properly you have to have a copy of
the relationships in there too.

Doris Manning
Database Administrator
Hargrove Inc.
www.hargroveinc.com


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Marcel Vreuls
Sent: Wednesday, June 04, 2003 8:57 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] relations in which database


Dear group,

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???

Thanks,

marcel vreuls


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Arthur Fuller
Sent: woensdag 4 juni 2003 13:09
To: AccessD
Subject: [AccessD] OT: Canon BJC 4200 printer problems


Does anyone have the printer mentioned? If so, would you e-me off-list
please? Thanks.

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com