I model a lot of my business objects after the West-Wind wwBusiness classes. I like to use them instead of tying data manipulation into forms as I often develop applications that have both web and fat client components to them. This is the prime example of using business objects across multiple front ends.
The wwBusiness object creates a THIS.oData object which is the scattered record from the back end, whether that's VFP, SQL Server, or something else. I'll sometimes scatter additive, and sometimes "hand add" a property with the ADDPROPERTY() function such as =ADDPROPERTY(THIS.oData, "foreign_pk", 12345) You mentioned that some cursor fields didn't get a property on the oData object. These weren't memo fields, were they? I often miss adding MEMO to the SCATTER NAME THIS.oDATA MEMO command. Kevin Cully CULLY Technologies, LLC Sponsor of Fox Forward 2006! http://foxforward.net Andy Davies wrote: > Michael Babcock said "What's the question? " > > I was mainly wondering how many people had tried 'scatter name this > additive' to build a data object. > > Like Michael I have tended to ignore the de but I am looking at oop design, > and it's there - I considered it for the 'home' of dataObj's but it seems > to be too closely linked to the form, then I came across the 'scatter name > this' idea and I was experimenting with the de in the role of busObj and > buiding dataObj's in this way. > btw early tests suggest that there may be 'features' in 'scatter name this' > - most of the cursor fields got themselves a property in oData *but a few > didn't*. _______________________________________________ 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.
