> > > Another "obvious solution" (delegating the use of the thesaurus to the
> > > client application) is also a non-solution : how do you join your data
> > > and the thesaurus data ?
> >
> > The usual way as in any relational data base: by referencing the information.
>
> That makes the client application a relational RDBMS with capability to
> access more than one database at a time. This was MS Access for us, up
> until now. And I would *love* to get rid of it ...
>
> > > The ability to "attach" (MS-Access parlance) a table or a view from
> > > another database is quite helpful. And I think that it has a lot of
> > > applications outside my (quite limited) realm.
> >
> > It is quite disastrous for referential integrity.
>
> Would you please amplify ? You might have a point, but I do not (yet)
> see it.
>
> --
> Emmanuel Charpentier
definitely isolating different databases is a non-practical idea, how can you image things will be changed
in future? do you believe that you'll never reference data in other databases? it sound likes that you are
still in 80's, in that time, PC are mostly not connected together via Network, when we need migrate data to
another PC, we should use floppy :(, this time I should use the barbarism method again --- dump table to a
file then load the file to another database even they are on same server! maybe I should write a stupid program to
do task periodically.
Regards,
XuYifeng
