John:

>>I think this is a mistake. Your insert stored procs could store @@Identity to an output variable. Then you get the new key. No need to round trip to the server...

I'm doing all my updates, deletes and inserts all at once in a batch, saves round trips to the server. The server is updated when a form is closed or when opening a new file or if the user just wants to. Primary keys are generated locally which saves even more round trips to the server. The only request I make for a unique key is at the start of an application.

>>In VB, you can create reusable data objects as well. As for the ineritence implication here, I don't find myself taking advantage of that with data objects. So, I see inheritance has irrelevent here

Not so here, my bases data objects handle all the parameter passing, server updating, checking for changes ect. In the future I'll just subclass them and save lots of development time!

>>A cursor is a VFP thing... To say that VB does not support is not entirely fair. I could drag a laundry list of items that are not supported in VFP. The fact is, VFP has a langauge geared toward DBF's, VB does not. And, with ADO Recordsets, you can much of the same sorts of operatons.

What I meant to say was a Record set and an output parameter. I'm equating a RS to a cursor. After all, the ADO client side cursor runs on the VFP cursor library, or at least this is what I have heard.


Charlie