Filepro-list Digest, Vol 36, Issue 17

[George]

-----Original Message-----
From: filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com
[mailto:filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com]
On Behalf Of Jeff Harrison
Sent: Tuesday, January 16, 2007 1:31 PM
To: George Simon; Tom Carey; filepro-list at lists.celestial.com
Subject: RE: Filepro-list Digest, Vol 36, Issue 17

 

--- George Simon <GSimon at americanriverintl.com> wrote:

>> You don't really _have_ to use an array.  You can
>> compare the existing and current fields when the
>> user saves the record.
>>  
>> George Simon Sr. Programmer
>> Information Technologies
>> American River International
>> 

> I believe that he wants to compare the current values
> to the original values - if you want to do that at the
> time the record is saved, then I believe that you do
> need an array to store the original values.

I don't think you do, Jeff.
When a user hits <Esc><Esc> to save the record and the processing goes to
the top of the table, filePro has not written the changes to disk yet.  I
don't think it does write to disk until the input processing table finishes.
So, at that point he can compare the existing field values against the new
field values and proceed accordingly.