It's a sobering experience to look back at a script written in Filemaker 4
about 10 years ago - no variables, no globals available across files, copy
and paste etc. One of my first scripts probably, and definitely due for a
complete re-write.

What the users have being doing all these years to deal with this bug, I
don't know. 



-----Original Message-----
From: FileMaker Pro Discussions [mailto:[log in to unmask]] On
Behalf Of Steve Cassidy
Sent: 05 July 2011 19:05
To: [log in to unmask]
Subject: Re: Import / locked record

On 5 Jul 2011, at 05:13, Peter Buchanan wrote:

> A successful manual import had me looking again at the script. At the very
> beginning of the import process, a variable could not be inserted into the
> locked record, which was then in fact being imported into FileB, but could
> not been "seen" from its new parent record, because the match field was
> blank.
> 
> Thanks to all the input - I now again have confidence in Filemaker's
import
> function, but my scripting needs some improvement....

Ah.... When you said that only 130 of 131 records was being imported, I
thought you were referring to the number of records in the imported found
set :) 

Glad you've worked it out, anyway.

Steve=