When importing new records into a db, Filemaker will usually write info to a file called "Import.log" located in the same folder as the db file. In the recent past, this would work for me. Now it is not working. Nothing is written to the file upon importing new records, no matter if there are import errors or not. I think I moved the file out of the folder, but I did move it back.

I am using FM Pro Advanced 11.0v2 on Mac OSX 10.6.5.

So:

1. How do you cause FM to start or stop writing to import.log (I can't find a preference for this)?

2. Can you change the name of import.log and have it still work?

Thanks,

Paul

In the recent past, this would work for me.

How recent?

http://www.fmforums.com/forum/showtopic.php?tid/209893/

It was working last month for me.

No, I did NOT see a button to open the import.log file in the import dialog notice (mine looked just like your screen shot), but the file WAS present and had been updated (located in the same folder as the DB file). At least it used to be updated!

I am just not sure why it stopped working or how to get it to start up again.

I have tried deleting the file and hoping it would be re-created upon the next import, but no joy.

It was working last month for me.

Are you sure you were importing records - not fields or tables?

Yes, I was importing NEW records from an Excel file into an existing DB file.

If the records are fine, I see them in the DB. If there are errors, the records are not imported. If there is a mix of good and bad records, I see the good ones imported and the bad ones are skipped.

Regardless, no changes occur to the import.log file.

Edited November 18, 201015 yr by Guest

That is my experience, too - except I have never seen the log created/updated when importing RECORDS.

---

That is, when importing records into an EXISTING table.

Edited November 18, 201015 yr by Guest

OK, I think you have got it. I just did an import that creates a new table and the import.log IS updated. So, I guess that the previous activity I saw in the import.log was due to other import operations, not simply record imports for existing tables.

Now, is this the way the import.log is suppose to work? It would be helpful if it showed which records were successfully and unsuccessfully imported!

Thanks!

Have you read the thread I linked to earlier?

Yes, I did read it and it describes the fact that no ERRORS are recored in the import.log upon importing records. The thread does not mention if the import.log is updated when records are SUCCESSFULLY imported.

So, I would still like to know:

1. Is there some way to turn off logging (or to turn it back on)?

2. Can we specify the name of the import.log?

AFAIK, the answer to all three questions is negative.