Filepro-list Digest, Vol 36, Issue 17

[George]

Nothing tricky, just do a lookup to the existing record using @rn.

-----Original Message-----
From: jeffaharrison at yahoo.com [mailto:jeffaharrison at yahoo.com] 
Sent: Wednesday, January 17, 2007 9:27 AM
To: George; 'George Simon'; 'Tom Carey'; filepro-list at lists.celestial.com
Subject: RE: Filepro-list Digest, Vol 36, Issue 17

 
--- George <flowersoft at compuserve.com> wrote:

[snip] 
> 
> --- 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.
> 
> 

Yes, it does not do the write until after the input
processing finishes.  However, I don't believe that
you will have access to the original values unless you
do something tricky.  How exactly would you propose to
reference the original values?

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHExport and JHImport.  The fastest and
easiest ways to export and import Filepro data.




 
____________________________________________________________________________
________
Finding fabulous fares is fun.  
Let Yahoo! FareChase search your favorite travel sites to find flight and
hotel bargains.
http://farechase.yahoo.com/promo-generic-14795097