>Oddly enough, in researching this I looked at Tastrade. Didja know they use APPEND BLANK in the AddNew method of the superclass? And in the DBC, there is a NewID function which grabs a sequential number from a "Setup" table.

I'm using this method lately, but newid() is not a SP, it's a separate .prg - which sort of protects me if someone is trying to add a record using plain Fox. The .prg is thus not in the database, and available only inside the .exe or our development environment. Probably a similar thing can be done with any updates, and there's the protection.

>Where this applies to your issues is that it runs headlong into a personal preference of mine: avoiding code in the DBC. I don't like procedural code in Fox DBCs, although when it comes to server databases I'm the opposite (tons of stored procs).

I've heard of the case where a programming team decided to keep all the programming logic (including business rules, RI etc) in COM objects, so if they switched from SQL to something else, they wouldn't have to rewrite all the SQL stuff. They've gone deep into SPs now, because this was dead slow, and they've all vowed loyalty to SQL anyway :)