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

[John Esak]

Joe Chason submitted a great wish list item. I voted for it being a
"must-have". He suggests a new command like COPY called MOVE. It would do
just that, MOVE a filePro record from one database to another and DELETE it
from the original file. The difference being that system maintained fields
would be "maintained" across the move. That is @cd, @ub, etc, would not be
lost. Very important for archiving... but, the question arises... How can
you maintain the @cd for example in the new file, when the record needs an
@cd for that file, itself??

I often look at my archive invoice file by @cd to see which were the very
last records just added to it and on what day...  How would I be able to do
this if the original @cd was kept with the new MOVE command.  JOe?

I want/need your suggested command, as you do, but how can we deal with the
reality of how filePro works?  Just lose the @cd of the MOVE'd record in the
new file??

John