Re: SEND / RECEIVE RECORD questions

2017-08-10 Thread Robert McKeever via 4D_Tech
I’ve done this a lot over the years. You send from a specific table. Likewise, you receive into a specific table. The receive goes in field order. Internally, the datafile keeps a mini-structure map for each record that is written at the time the record is written. Then, if you change a field f

Re: SEND / RECEIVE RECORD questions

2017-08-10 Thread Kirk Brooks via 4D_Tech
Miyako, Thanks for the reassurance. Does the matching work based on the table/field names or numbers? On Thu, Aug 10, 2017 at 2:05 PM, Keisuke Miyako via 4D_Tech < 4d_tech@lists.4d.com> wrote: > RECEIVE R. command is capable of processing records sent from pre-v11 > versions, > it looks at the he

Re: SEND / RECEIVE RECORD questions

2017-08-10 Thread Keisuke Miyako via 4D_Tech
RECEIVE R. command is capable of processing records sent from pre-v11 versions, it looks at the header and converts ANSI to Unicode text as necessary. > 2017/08/11 5:51、Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> のメール: > And what about changes across 4D versions? Like attempting to RECEIVE > RE

SEND / RECEIVE RECORD questions

2017-08-10 Thread Kirk Brooks via 4D_Tech
Hi folks, I have never really used SEND RECORD and RECEIVE RECORD. I get the theory of it and the docs explain the mechanism. I'm wondering what happens when you attempt to use them and the structures have changed? Or tables or fields were re-named? And what about changes across 4D versions? Like