Hi Bonnie,

>>Well doing it in one procedure only makes sense if you make use of the autoincrement feature. It becomes more complicated when you want to insert an order with orderlines into one transaction where you have to know the order_pk in the orderlinestable before you insert the records.

>All your "basic" SPs would have the PK as an output parameter. You'd insert your parent record, getting the new PK returned as an output parameter, and then you'd be able to insert your child records.

Wouldn't you agree that having two remote views used for client input with predefined PKs (from a generation table) would be far easier than having to write routines in VFP that will handle this proposed mechanism ?

From the VFPs developer standpoint of view I see no benefit in programming efforts not flexibility nor back end transparancy.

You might have some points regarding security, performance, and better support for other programming languages that don't have a lot of other options connecting to the database, nut in general I agree with JohnR remote views seem to be more flexible here. In cases where remote views fail I might use SPT, but I would not use SPs for just regular updating tables: too clumsy.

Walter,


>~~Bonnie