>Hi all,
>i am currently working on software which has divided up its tables over 5 databases. all the tables inter-relate with each other between the databases through code (ie. two databases opened and a table opened from each and a relation is established through code).
>going on this setup, i can't for the life of me figure out why in the world they split up the tables into 5 databases. is there any benefit in doing this??
>
>i ask because i am changing over to using ADO controls and i don't want to have to create more connections than needed.
>
>Jordan :)
I've seen this done. Generally, it's due to PPD (pretty poor design). However, it is possible the databases could be used in independant sub-systems. That, IMHO, is the only viable reason.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
