Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
The m. or tableUpdate() approach
Message
 
To
27/10/1996 10:51:35
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
00010138
Message ID:
00011003
Views:
37
>>
>>TableUdate() most of the time if not always. Use scatter/gather if you have a set of data you wish to keep in memory for reference -- Use the new NAME option to stays OOPish (s). You also have OldVal() & CurVal() you can play with.
>>
>>Tom
>
>The problem with NAME is that not operate on memo fields.... It is true? Some workaround?

Angel "Java" Lopez

Seems like everything worked fine if I remember right. Actually it works better with the Name clause -- much more power.

Tom
Tom
--------------------------------
Tom O'Hare
407-299-4268 -- tom@redtile.com -- http://www.redtile.com/
Independent Programmer Using Visual FoxPro, Visual Basic & more...
Operations Manager -- Virtual FoxPro User Group (VFUG)
http://www.vfug.org/ -- tom@vfug.org
President -- Central Florida FoxPro User Group (CFFUG)
http://www.redtile.com/foxpro/
Universal Thread Most Valued Professional (MVP)
http://www.transformation.com/foxpro/
Previous
Reply
Map
View

Click here to load this message in the networking platform