Importing w/ Field mapping goes wrong

[Scott Pon]

I have a Customer List that is stored on my accounting software program. The Customer List is then exported to a .PRN file (basically a text file). Then I import the data into Filemaker. I use Field Mappings to make sure that the fields all match up. Each of the Customers in this list have a UNIQUE Customer Code. So I set up the Database with a field "Customer Code" and then map the 2 fields together.

It is supposed to import the data according to the customer code then update the record. If it does not find the Customer code, then it adds it to the list.

I also put a script to automatically do this importing. Accounting will be doing this so I needed to make it a simple 1-button action.

But here's the problem. it doesn't work all the time. The weird thing is that sometimes it imports correctly. and other times it can't find the match, and adds the entire list again into the database.

is this a bug in filemaker??? Anyone else experience this problem? is there a fix?

Or am I losing my mind???

I also have 2nd DB that does the same thing, except it holds the Shipping addresses of the Customer.

If you need more information, please let me know I'll be glad to give more info and details to the problem.

Thanks.

[QuinTech]

Accounting will be doing this so I needed to make it a simple 1-button action.

LOL

Hi, spon. I suspect the problem has less to do with the script than the relationship. Are you absolutely sure that the Customer Codes match at those times the import is not operating properly? No extraneous characters or anything? Verify that from the "holding-tank" database you import the .prn into directly.

Jerry

[Scott Pon]

LOL

Yeah yeah yeah... they are good at accounting. not programming

I see what you mean. I should use a "holding tank" database, and import all the records into there. Then from there import all the data into the Customer Database. That is something I will try. I will let you know what I find in my tests.

Thanks!

[Scott Pon]

It has been 1 week since I implimented this and there does not seem to be any problems! so the "holding tank" did it! Thanks for your advice and help!

[-Queue-]

Another thing to note, make sure the database into which you're importing has all records found before the import. Updating only works for records in the found set.