729 error on import

[tomp]

I'm going crazy. I have been developing a script that imports a comma-separated text file. The import had been working, I saved a version of the file, and I continued working on processing the imported data.

When testing, I started getting 729 errors, "Errors occurred during import. Records could not be imported".

I've recreated the .txt file, modified the import script step, tried a direct file import, re-installed my developer 7 program, went back to the 'good' version of the file that had worked, created the text file as tab-separated to try importing it as tab-separated text, and anything else I could think of. I always get the 729 error.

When I import the file into the FM6 version of my application, there is no problem.

I've tried it with other data sources (the .txt can come from any number of places) to no avail so it is not just the one data set.

Can anybody offer any suggestions?? I'm really at a loss of where to go from here.

TIA.

[SteveB]

Version 7 is still pretty buggy, which I gather from reading about all the problems. Have you checked the FM Site for this error message, and have you installed the latest patch?

Steve

Edited July 31, 2005 by Guest

[Reed]

Are you doing the import with a runtime?

If so, does the problem only occur in the runtime, or if you import directly into the file opened with FMD too?

If you just make a new file that only has the fields necessary to import the text, does the import error happen with a clean .fp7 file?

Finally, does the same error occur both on the Windows and Mac versions? (or at least on more than one computer)

[tomp]

I went to FileMake Knowledge base but couldn't find anything.

I will be doing the import in runtime (if I can get it to work) but I'm encountering the problem in 'normal'(?) mode - both when performing a script and when doing a 'file/import records' directly.

It does occur on more than one MAC(panther). I did not try on XP

I created a new .fp7 with just the necessary fields, created a simple script (capture error on, import, capture error off) and am able to import without error. Sounds like a file corruption of some sort. Looks like I'm back to recreating the file. Sure hope I can import the scripts!!! I'll be sure to save versions that work incrementally.

Thanks for the suggestion to create a stripped down .fp7!! I'm sure glad there is just one table in this file (other parts of the solution have MANY tables). I'm glad I segregated the data for import.

Do you think FM would be interested in the 'bad' file and a sample .txt file to trouble shoot what went wrong??

tomp

[tomp]

P.S. The bad file is the only file in this application that I did NOT recreate from scratch when converting from FM6. I took the converted file and updated it to properly relate to other files in my redesigned FM7 solution. A clue to the cause of the failure??