great new wish list item, but how will it really work?

[GCC Consulting]

-----Original Message-----
From: filepro-list-bounces at lists.celestial.com
[mailto:filepro-list-bounces at lists.celestial.com] On Behalf Of Mike Schwartz-PC
Support & Services
Sent: Thursday, April 22, 2004 10:29 AM
To: 'filePro mailing list'
Cc: wishlist at fptech.com
Subject: RE: great new wish list item, but how will it really work?

 
> if to allow partial changes, how about something like:

> MOVE xyz WITH (system,maintained,fields)|ALL

	The biggest bane to COPY/MOVE is the field mismatching possibility where
somebody may have added or changed a field in either the master file or the
archive file, and not made a corresponding change to the other file.

	So, I would like to see a command like:

COPY (or MOVE) checkfields|nocheck

which would give an error if the field lengths and edits of the two files did
not match.

	For compatability with existing code, I guess just adding the
checkfields option would be the best thing to do.	

--------------------------------------------------------------------------------
-------------
Take the above 1 step further, if the difference is with the "archive file"
needing to be updated, add an option to run autoshuf to correct the archive
automatically.  

One could program this by
 if: checkmap = "N"  (maps are different)
Then: ab="copy map ..\archive\map.new";ac="\fp\autoshuf archive"
 if:
Then: system ab;systen ac;GOTO arc_rec

Now I realize that fp offers the commands to copy the map internally, but I
don't use these often, so someone else could post this command structure.

By the way, it may be possible to write such a routine from within fp.  This may
be an interesting project.

Richard Kreiss
GCC Consulting