I noticed that although I've checked all the check-boxes, when importing a CSV file, FMP does not populate the auto-enter PK field, except for the final row.
Any way around this?
What is the auto-enter field? Are you trying to import INTO that field from a CSV column?
Can you post screen shot(s) of dialogs that you are using to set this up?
The auto-enter field is the PK for the table and not part of the import itself.
The import imports two fields, but the separate auto-enter PK is set to generate a new serial number on new record creation.
(It's just that the auto-import field isn't doing what it should be: generating a PK on record creation. Sounds like a BUG to me.)
The only times I've seen this happen was when Perform auto-enter options while importing was NOT selected. If you suspect there is a bug with that, let us know how to reproduce it.
It's a simple CSV file and here is the auto-import:
and the PK field in question is defined thusly:
I'll try to put together a separate test outside the app and report back.
This is really strange.
I've included the actual CSV file in question below.
And, I created a script with a single import statement and made sure that the auto-enter calcs checkbox was checked.
The database is defined like this:
The script is this:
Import Records [ With dialog: Off ; “review.csv” ; Add; Mac Roman ]
Here is the database table after the import:
Review Period, Review Percentage,
10 days, 55.33,
30 days, 99.32,
3 Years, 88.71
Can anyone else reproduce this issue?
Can you screen shot the import dialog showing the field matching? You have a "," at the end of some of the records. I wonder if this is "mapping" to the PK field and somehow "importing" a blank column value?
A CSV should look like this:
Review Period, Review Percentage"10 days",55.33"30 days", 99.32"3 Years", 88.71
Review Period, Review Percentage
"30 days", 99.32
"3 Years", 88.71
Are you using CSV or TXT? (what extension on the file and what type of file to import) - the screen shot of the dialog would help here.
Yes, I just had a blank item with "=>" pointing at the PK field.
It happens to all of us! That's why this forum is amazing. We need to remind each other about all the things we forgot.
Come on back any time!
Retrieving data ...