Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 7421 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I AM USING FM7 (this used to work in FM6)

I have (2) databases

During a script, i find one record in 1 database

the script then goes to the 2nd DB and runs an import records script from that databse (subscript)

But it imports ALL of the records not the "found set" of records?:?

How do i get it to just import the found set (in this cast just 1 record) and not all the records?: mad.gif

Thanks

Wade

  • 2 weeks later...
  • Newbies
Posted

I have the same problem. The most strange thing is that I could import only the found records when I used it in my local machine, but when I used it through the Filemaker Server all the records were imported.

I will really appreciate any help.

Posted

In FM7, Import will import all records from a closed database or the found set from an open database.

Posted

I haven't tried this, but I think this is it:

Have your destination file (the one that is performing the import) open the source file on the server and execute a script in the source file. The script in the source file would simply find the correct set of records in the right table. Then have the destination file run the import, specifying the source file and table. This can all be scripted.

  • Newbies
Posted

When I selected the File in the Filemaker Server by clicking "Add File..." button for the Specify data source of Import Records script, the relative path (file: filename) is shown on the File Path list. But when I click on the OK button, I got the error message "The file cannot be found..". So I could close the window only after I added the Filemaker Network path (fmnet:/IPaddress/filename). But after I added the Filemaker Network Path, my script always is importing all the records, not the found set.

I have been spending a whole week to find the solution, but I still cannot find it. I will really appreciate any kind of help.

Posted

It's a known bug, and a substantial one. You are not going to fix it. You'll have to wait for Filemaker Inc.

This topic is 7421 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.