AnsweredAssumed Answered

Scripted spreadsheet import (Excel 2003 Win) stopped working with internal error 729

Question asked by PauloNascimento on Oct 27, 2010
Latest reply on Oct 28, 2010 by philmodjunk

Summary

Scripted spreadsheet import (Excel 2003 Win) stopped working with internal error 729

Product

FileMaker Pro

Version

10 & 11 Advanced

Operating system version

Mac OS X 10.6.4 Snow Leopard and Windows XP Professional SP3

Description of the issue

A previous working import script stopped working properly.
The caught erro with Get(LastError) is 729.
Filemaker 729 error description is:

Errors occurred during import; records could not be imported.

Wich does not give proper clues for convenient troubleshooting. Steps already attempted:

1. Recover DB with consistency check (no errors found)
2. Tried to recreate the import script (fails miserably too)
3. Manual import (same results with the important detail that UNNAMED/UNKNOWN fields appear in the standard "Import field mapping" dialog.
4. Importing same spreadsheet into another empty database or table works great as expected.

Help appreciated, this is my major issue with FileMaker in almost 20 years of use. Don't let my faith go way please...

Steps to reproduce the problem

Execute the script (via layout button) which contains an Import Records step.

Expected result

Added records in current table, from source spreadsheet file.

Actual result

All records skipped. Ilogical.

Exact text of any error message(s) that appear

Erro 729.

Workaround

Not yet.

funkyFMPAError27102010.png

Outcomes