Relationships, where? Back or front end??

[Marco]

Hi. In terms of performance, where should I create the relationships? In the
back-end or front-end?

I've got a front-end/back-end solution in my company with a lot of users
working on it.

So, I wonder what is best, put the relationships in front-end, so it would
work local or in the back-end and use the network, which could put my network
slower.

Thanks,
Marco

 

[Albert D. Kallal]

Hi. In terms of performance, where should I create the relationships? In
the
back-end or front-end?

I've got a front-end/back-end solution in my company with a lot of users
working on it.

So, I wonder what is best, put the relationships in front-end, so it would
work local or in the back-end and use the network, which could put my
network
slower.

You actually find that you can't create the relationships in the front part.
However, what would happen if two different front ends with different
enforced relationships opened the back end? It would be too confusing...

Simply put, the settings in the front end do nothing, and it is the ONE back
end where you define the relationships. You don't have a choice in this
matter....

The one back end is the boss here....

 

[TonyT]

Hi Marco,

The back end should contain just the tables (in access), any relationships
between the tables should be created here in the relationship window. This
should live on a shared drive in the server.

The front end should contain all the forms, reports, modules and queries and
should reside on the client users pc.

hth,

TonyT..