> 1. Re: oop? (MB Software Solutions) > Message: 1 > Date: Thu, 09 Nov 2006 10:58:37 -0500 > From: MB Software Solutions <[EMAIL PROTECTED]> > Subject: Re: oop? > To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > Andy Davies wrote: > >> 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 > >> > > > > Kevin, > > thanks for the reply - and yes you're right - several were memo fields and > > one clashed with an existing property. > > Now I've done a bit more testing I think 'scatter MEMO [blank] name this > > additive' has definite possibilities. > > > I definitely make use of SCATTER/GATHER to move single records amongst > my tiers. For grids, I still reference the underlying cursor, but for > validations and single record adds/updates, I use SCATTER/GATHER > exclusively. > > I've got the MySQL side of things working in my most recent app, and am > working to make sure the VFP side works now too. Once that's done, I'll > release the entire source code here for others to review and make > comment if they wish. > > --Michael
Hey Michael Something I've often wondered about. Most data objects seem to map to a single record and then an exception is made for dealing with a grid. SQL says the model for data is a cursor one or more records. Why are data objects not using a cursor object to hold one or more records? Mike _______________________________________________ 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.
