Imported records to new found set

[fishtech]

Hi,

FWIW, I came up against this about 18 months ago, but I just cannot remember how I worked around it... ugh!

I'm importing records from a FMPro local file to a FMPro file hosted on a server. I need to mark the imported records with a date after the import.

If I do this manually, the imported records automatically show in a new found set of imported records in the server file. then they are easy to mark.

However, when I script this import as part of a larger routine, the imported records are appended to the existing records in the server file. They do not show in a discrete found set, or even the existing found set.

Can someone please remind me how to workaround this?

Many thanks,

ft.

[Søren Dyhr]

Everything synchronizing stinks and are likely to fail at some point, couldn't you approach a served file via the protocol only ... is it an "outside coverage" problem?

--sd

[Fenton]

Another method to add constant data to a field upon import is to set a global field in the originating file/table, and import that value into a regular field in the target file/table. It's faster then a post-import Replace operation, and less prone to trouble (except forgetting to set it).

[comment]

I agree with Fenton. And you could also auto-enter a global or a variable.

However, I believe you are mistaken when you say:

when I script this import as part of a larger routine, the imported records are appended to the existing records in the server file. They do not show in a discrete found set, or even the existing found set.

I think that immediately following the import, and before you continue with the rest of the routine, the found set should contain only the last import batch.

Edited April 9, 2008 by Guest

[Fenton]

I had a question, somewhat related, which I should know the answer to, but don't really. What about if another user creates a new record? Would it appear in your found set? I'm concerned with this in long batch operations, say a very lengthy loop on a found set.

[comment]

In which scenario?

[fishtech]

I'm using 'Debug scripts' to step through the script.

The script is...

Go to Layout [ “Deletions” (Deletions) ] 

Import Records [ Source: “filemac:$$file”; Target: “Deletions”; Method: Add; Character Set: “Mac Roman”; Field 

[ No dialog ] 

Before 50 records are imported the destination layout shows:

Record: 1

Found: 1000

Total: 5000

After 50 records are imported it shows:

Record:1

Found: 1000

Total: 5050

Should this be different out of debug mode?

Regards,

ft.

[fishtech]

Thanks for the suggestion.

I will see how this topic progresses but this sounds like a good way forward.

Thanks,

ft.

[comment]

I don't run a server so I cannot say for sure, but it seems very weird to me. I believe importing should end with a found set of imported records - manual or scripted, debugger or not. Are you all patched up with the latest updates?

[aldipalo]

I confused (Nothing new : ). If you have a DateCreated field and set it to auto Enter 'Creation Date' when you import a record and tell it to 'Perform Auto Enter Options' the date will be there and you will see only the new records as your found set. Am I wrong about that?

[fishtech]

Yes, the imort 'auto-enter' options will automatically add the date.

However, there is no granularity allowing the user to choose which fields should be auto-entered at import.

Other fields including lookups, 'created by', auto-enter serials, etc would also be auto-entered. This would not work well in this solution.

Regards,

ft.

Edited April 9, 2008 by Guest

[comment]

I believe so. Although I wouldn't use this method to mark import batches, because if the import is performed around midnight...