Riddle me this...

If I set up a database - Field1, Field2, Field3

with one calculation Field Field4= LeftWords(Field2;1)

and one auto-entry Field5 : auto enter serial number

and import a text file with 3 CSV fields

If I do a plain old import, add new records, perform auto entry then the text comes in as expected. Fields 1-5 are all filled in.

If, however, I do an import with "update matching records in found set" (where I have all records showing) and have "add remaining data as new records, things don't import as i would expect. Field5 does auto enter a serial number, but Field4 does NOT calculate, and does not fill in.

I very much need it Field4 to do its calculation. What am I missing?

Can you post a sample file with your problem? I cant not replicate your problem.

Try:

Field4 = Evaluate("LeftWords(Field2;1)";Field5)

Here's more info as I've messed with the import window.

When I import with update matching records turned on:

if I have the = sign next to Field2, telling it to match records based on this field, Field4 *will not* perform its calculation

if I have the = sign next to Field1 and Field3, then Field4 *will* perform its calculation

JA

It seems LOGICAL ! :

I'm not so sure.

If Field2 is the one I need to match on and Field 2 is also the vital field that all my calculations inside the database are based on, then I'm screwed. (Luckily in my practical application I can use the Field1 and Field3 to match on.)

But, does it make sense that Filemaker won't do the calculations based on the data imported in this field if it is used as a match field? And why? What good thing does it serve that I am missing?

JA

I second mr vodka's suggestion.

Ok, if i did this right there should be a .sit file attached.

A small database and an example of text file I'm using to import.

If you import using the settings in screen shot one, Field4 will not fill itself in.

If you import using the settings in screen shot two, Field4 will fill itself in.

JA

I cannot reproduce your problem. Is your app patched to 7.0v3?

No, I'm 7.01. I will upgrade and try the same thing again. Thanks

JA