[AccessD] relations in which database

That sounds screwy to me, not logical.  The front end has to deal with
the backend tables anyhow, so I don't really see what difference the
location of the relationship is going to make in performance.  All the
queries are processed in the front end regardless.

Charlotte Foust

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


Hi Charles,

The advantages are not mine but I got them from several 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


gr marcel





-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Wortz, Charles
Sent: woensdag 4 juni 2003 15:05
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] relations in which database


Marcel,

Since relationships are between and among tables, and since the tables
reside in the BE, why do you think the relationships should be in the FE
and not the BE?  Also, I do not understand your so-called advantages?
Please explain.

Charles Wortz
Software Development Division
Texas Education Agency
1701 N. Congress Ave
Austin, TX 78701-1494
512-463-9493
CWortz at tea.state.tx.us



-----Original Message-----
From: Marcel Vreuls [mailto:marcel.vreuls at oop.nl] 
Sent: Wednesday 2003 Jun 04 07:57
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
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com