I agree. SCATTER NAME is more contained and I have never had problems with it. It is also easier for debugging as the MEMVARs don't appear all over the alpha-sorted memory list.
Henry -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charlie Coleman Sent: 2008-05-05 2:57 PM To: [EMAIL PROTECTED] Subject: RE: VFP7: Gather memvar fields not working At 01:25 PM 5/5/2008 -0400, David Crooks wrote: >On Monday, May 05, 2008 1:20 PM Paul McNett wrote: > > >Is field3 a memo field? Do you issue GATHER MEMVAR MEMO? > >No. No memo fields in the table. The worse part is that it works when I >step though the code but not in production. I guess it is time to This may not apply, but if you're doing just a SCATTER MEMVAR, you're subject to all the potential conflicts with other regular memory variable names (if I understand it correctly). For example, if you've got a field called cData_stuff, you may have a memory variable you've created yourself called cData_stuff. I've not tested what happens when things collide like that, but given the potential of public, private, etc scoping, I've opted to just not use SCATTER MEMVAR. I always add the NAME clause: SCATTER ... MEMO NAME oMyTempRec and the corresponding GATHER....MEMO NAME oMyTempRec (and I generally declare oMyTempRec as a LOCAL variable). I've never had a problem with that approach. -Charlie _______________________________________________ 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 Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** 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.
