Bob
If using Client server databases, relations etc should definitely be set up in the server database.
We use (and like) RVs a lot because it allows us to develop for multiple sites and backends without having to cut special versions or apps for each site. For example: hospital A may use Patient Management System B with database C and lab system D while hospital Z uses Patient Management System W with database X and lab system Y. Using RVs means you can put the logic required to manage these variabilities into a site DBC and keep your application generic and the same for all sites.
We have 1000-bed hospitals using our RV apps widely without trouble.
Regards
JR
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
