You'll need to share more details.
What kind of import?
Scripted or manual?
Do any of these imports attempt to update matching records or do they always add just add new records?
Do you check the dialog that appears after import (manual) to see if all records successfully imported?
If scripted, do you check for any error codes returned by the import?
Issues with getting the correct found set can affect imports that use the matching record option to update matching records.
Validation field options, if the "validated always" option is set can keep some records from importing if they fail a validation option.
2. it's all add new records , no update
3. we will implement error codes checking in our script. let you know later.
That basic rules for importing data are:
- if a field validation fails and the field data can be dropped then it is dropped
- if a field validation fails and the field data cannot be dropped without breaking validation rules then the entire record is dropped.
after cleaning the hard drive C: which is a bit of full ( clean a lot of temp files ) .
then run the update is fine for now.
-- so it kind of tell me that the server or filemaker in general use "extra" hard drive space when doing importing from one file to another? and if the hard drive is too full, the data will lost in transaction ?
-- anyway, we will keep the hard drive in "healthy" mode. but just curious how it works.
The lesson is to have sufficient free space on your main drive. FileMaker uses a temporary copy of the file at all times. Periodically, the temp file is synched with the file on disk. This means that you may need significant amounts of free space for some operations.
Yes, but if you run out of room for temp files, you should get an error message popping up. I really would not expect the lack of space for temp files to affect the results of your record imports unless you also were getting error messages about available free space.
I suppose that a corrupted temp file, however, might be able to cause such problems.