>This question came up at work: Can a DBC be classed like an object? And would it be handy to instantiate a DBC? Seems that instantiating a DBC with rules, triggers, views, etc. might be handy - Or does this make any sense?
Two thoughts here...all of the DBC properties are obtainable through DBCGETPROP which sort of eliminates the need to class it. IMHO. The second is that, well, a DBC doesn't really fit the (my) definition of things to class. A DBC is metadata regarding tables, views etc. In and of itself, it has no reason to exist as a separate object.
Now - if we could instantiate data objects directly from the DBC, rather than having to define them from scratch in a VCX - THAT would be cool.
Just my $0.02 worth...
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.
