But there is a caveat.... I don't remember exactly, but it has to do with=
=20NULL values in some fields. They will skew the compobj return value.
I'll have to check on it...
-----Original Message-----
From: profox-bounces AT leafe .D.OT com [mailto:profox-bounces@leafe.com]On
Behalf Of Desmond Lloyd
Sent: Thursday, June 12, 2003 2:23 PM
To: profox AT leafe .D.OT com
Subject: Re: VFP7: Checking for Changes Made by the User
Thanks Jerry!
Interesting approach. The way some of this code is written and the forms=
=20
are tacked together this presents a definite viable alternative. So=20
COMPOBJ(thisNAME,thatNAME) works with named scattered records? (obviously=
)
All the other suggestions and the discussions have been great! (still=20
reading all of them)
Desmond
8-)#
>From: "Jerry Ott" <jkott@sbcglobal.net>
>Reply-To: ProFox Email List <profox AT leafe .D.OT com>
>To: <profox@leafe.com>
>Subject: Re: VFP7: Checking for Changes Made by the User
>Date: Thu, 12 Jun 2003 10:57:38 -0700
>
>I guess there is always the old philosophical question about how to coll=
ect
>information from a form. I always use the SCATTER NAME to NEWVAL for my=
>variable entries and also SCATTER NAME to OLDVAL for comparison purposes=
.
>When I'm through I use COMOBJ(NEWVAL,OLDVAL) to see if any changes have =
>been
>made.
>
>Jerry
>
>
>
[excessive quoting removed by server]
©2003 John Baird |
