I have an import script that uses a $path to a local copy with the same file name to import into a served copy of a file. Designed and working in version 10. Version 11 seems to have broken the ability to import from a file with the same name via this method. I have just used version 10 instead of figuring out if there is a way to make it work in v11.

Cheers,
Joel Bowers

On Tue, Oct 19, 2010 at 11:39 AM, Stephen Wonfor <[log in to unmask]> wrote:
Sue

Just took a look with FMP11A from one database to another.  The import shows the found set (15 of 2,514) when I load from a base table in one file into a base table in the other.
I do Anchor Buoy design (www.kevinfrank.com/anchor-buoy.htm or http://sixfriedrice.com/wp/six-fried-rice-methodology-part-2-anchor-buoy-and-data-structures/) so I always have base tables, they are the only tables I use for the context for a layout.  When I do a find on a layout it is inherently in the context of a base table - thus it honours the data in that table and is not a "view" of the data via a relationship.
The key might be in the context of the layouts.  If your layout is based on a non-base table (a Buoy in the AB design) I think it may be possible to not get the found set correctly.
If your design is not AB you may need to base your imports from purpose build layouts that rest on a context defined by a specialty base table. eg.  You might have a Contacts table but you would use ContactsExport base table to do finds upon.

I do a lot of inter-db imports this way.

If that still fails you might consider using a "one-time" key to write data from one db table to another via script.
eg. Set Get(CurrentTimeStamp) into a global and add a $Counter - eg. "10/29/2010 17:00:32 Count 1".
You would loop through the found set incrementing $Counter each time and update the global (with a Commit).  You'd have a join between tables that allowed creation of related records.
This works well - the only persistent issue is auto-enters in the receiving table (they can be handled but you need to be aware of them).

Stephen

----------

"The physicist's greatest tool is his wastebasket."    — Albert Einstein

On Oct 19, 2010, at 11:13 AM, Sue wrote:

> I am having a hard time getting Filemaker to import just the FOUND set of records from one Filemaker table to another FM table in a different File.  I want just 7 out of 126 records, so my script opens the first file and runs a Find script that locates the desired 7 records in the first file.  Then my script (which is run from the second file) imports records from that table to the new table in the second file.
>
> Only one window is open in the first file and only the 7 records I want are found and showing in that window.  Yet I still get 126 records imported to the second file.
>
> Arg.  What do I need to change to get this to work right? I am sure I have been able to do this sort of thing in the past.  What am I doing differently, or what do I have set wrong?
>
> (Just upgraded to FM 11, but I don't think that is the problem.)
>
> Thanks for any help!
>
> Sue



--
Joel Bowers