Steve Ellenoff wrote:
> Funny, I was literally thinking about this the other day myself. What 
> prompted you to go this direction?
>   
I was using objects for single record viewing as well as processing 
single record insert/updates in views.  So when passing my objects along 
my tiers (UI --> Biz --> Data) I found it so easy to just use INSERT 
INTO MyTable FROM NAME toRecord as well as making use of SCATTER/GATHER 
too.  In addition, for non-VFP backends, I was getting an empty 
recordset/row from the remote table, inserting my fields, and using Paul 
McNett's MakeUpdatable.prg utility (found in the ProFox downloads 
section) to automatically do the insert/update like a remote view.

> Are you binding the view also to your forms and then simply creating 
> the update sql statements at save time, or using objects for the 
> binding, in which case, I don't see why you'd use the view.. :)
>   
I'm using views basically for grids, where it's many records to show at 
once.  However, I'm experimenting sometimes with using the dirty buffer 
status of the records (via GETNEXTMODIFIED) and then scattering to a 
record and SEEKing against a VFP table and then doing a GATHER, or, for 
non-VFP, using the MakeUpdatable.prg as I mentioned above.

> Have you run into any gotchas along the way?
>   
None that stand out in my head at present!


-- 
Michael J. Babcock, MCP
MB Software Solutions, LLC
http://mbsoftwaresolutions.com
http://fabmate.com
"Work smarter, not harder, with MBSS custom software solutions!"



_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to