🚀 go-pugleaf

In article <29SEP199211203420@vxcrna.cern.ch>
sandrov@vxcrna.cern.ch (VENTURA,SAND./EP) writes:
 
>
>In article <michaelh.717718108@Xenon.Stanford.EDU>, michaelh@Xenon.Stanford.EDU (Mike Hennahane) writes...
>>sandrov@vxcrna.cern.ch (VENTURA,SAND./EP) writes:
>>
>>>I'm experiencing some troubles with the Receive Record command:
>>>I can't avoid it to create a new record each time it executes, despite what
>>>stated on the manual which says that a record can be received in the current
>>>record.
>>
>>the manual says that you must create a *new* record for the file
>>before you do a 'receive record.' i don't think that you can receive a
>>record into the current record.
>
>In fact the example in the manual shows how to receive by creating a new record.
>But the description of the command (I'm one of the lucky men which works
>with a reference manual in french, while scripting in english :-)
>states "Si vous recevez cette fiche dans une fiche existant deja, les
>anciennes valeurs des rubriques seront remplacees par les valeurs recues
>(i.e. If you receive a record into an existing record, old field values
>will be replaced by received ones)". Which seems to be doubtless! Moreover, in
>the multiuser section there is a warning about being sure to work on a
>non-locked current record when receiving...
>>
>>>What am I missing? Any help or more general suggestions on how to transfer
>>>records between separate databases?
>>
>>are you transferring new records, updating existing records, or both?
>>
>>--mike
 
<Stuff Deleted>
 
 
With version 2.2.x (maybe 2.1, I don't remember), the recieve record no longer
requires you to create a new record to recieve into.  This is automatically
done by recieve record.  In english:  recieve record now automatically creates
a new record.  You still must execute save record to ..ahem.. save the record.
 
 
Bill
st25370@vm.cc.latech.edu
rwj@engr.latech.edu