>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?

I think it makes sense. We do it so we can recreate the dbc if it gets blown away and so we can store the prg in SourceSafe that will recreate our dbcs. I've never subclassed one, though, but it could be done. One of the developers here came up with a program called GenDBCX, a hyped up version of Microsoft's GenDBC.prg. It will generate the prg you need to recreate an existing DBC. I looked in the files section here on the UT and didn't find it, though. I'm sure somebody here on the UT can tell you where to find it, if you're interested. Since I've been working with Oracle, I've had to use code to tweak many of my remote views using code because of the limitations of the database designer and my ODBC driver. The outer join syntax in Oracle is different from that in VFP. My ODBC driver didn't do a good job in translating outer joins into Oracle syntax. Using code, I was able to write the remote view in VFP using Oracle syntax. I couldn't have done that database designer.