Recently starting working on a file I positioned on my XP desktop... and noticed that periodically, an "import.log" file appears sort of magically even though I didn't do any importing.

The contents vary but it always refers to "import operations started" and usually mentions clipboard...

Here's a sample

[color:blue]11/28/2005 4:50:26 PM, SPARK2.fp7, 0, Import operations started

11/28/2005 4:50:26 PM, SPARK2.fp7, 0, Import operations started

11/28/2005 4:50:26 PM, SPARK2.fp7, 0, Import of script steps from clipboard started

11/28/2005 4:50:26 PM, Rpt_CallSumByCode, 0, script steps imported 1

11/28/2005 4:50:26 PM, SPARK2.fp7, 0, Import completed

11/28/2005 4:50:34 PM, SPARK2.fp7, 0, Import of script steps from clipboard started

11/28/2005 4:50:34 PM, Rpt_CallSumByCode, 0, script steps imported 1

11/28/2005 4:50:34 PM, SPARK2.fp7, 0, Import completed

11/28/2005 4:50:47 PM, SPARK2.fp7, 0, Import of script steps from clipboard started

11/28/2005 4:50:47 PM, Rpt_CallSumByCode, 0, script steps imported : 1

11/28/2005 4:50:47 PM, SPARK2.fp7, 0, Import completed

11/28/2005 4:55:48 PM, SPARK2.fp7, 0, Import operations committed

11/28/2005 4:55:50 PM, SPARK2.fp7, 0, Import operations committed

11/28/2005 4:55:50 PM, SPARK2.fp7, 0,

Anyway, try as I might, I can't seem to catch the creation of this file right when it happens so I don't know what's doing it.

Anyone know of a detailed article or something somewhere that unveils the great secrets of the import.log? I'm just concerned that I may have some automation going haywire and doing imports willy nilly when I don't want them to happen!

Are you perhaps importing scripts or copy/pasting script steps when this happens?

I think I may have cut/pasted script steps within a script ... I know I wasn't doing any importing from the menu, that's why I'm surpised to keep seeing the log appear.

Seems kinda weird at first, but when you copy/paste tables, fields, or scripts - it's technically importing/exporting these things. Hence the log file. Mine is getting very long now : The only real way to clear it is to delete the file. Next time you perform such tasks, it'll just create another one.

Thanks for the info. That's exactly what's happening.

Someone at FM should add an entry to the help file under the heading "import.log"!

Save a few of us some wasted anxiety.