I am converting a database from v6 to v8. Within the database, there is an import script. In v6, self-join lookups in the destination file were triggered. In v8, these lookups are not working - those fields are just coming up empty.

I have tried changing lookups to auto-enter calcs, but no luck.

In v8, are records not committed until the import is completed, rendering self-join lookups useless?

Thanks in advance for any advice...

During the import are you promted for measures regarding the autoenters, be it calc's or lookups....

However have repeating fields changed behaviour ...as far as I remember.

--sd

I do have "Perform Auto-Enter Options..." selected. Lookups from other tables are fine - it's only the self-join lookups that aren't working...

Refresh my memory on why such issues mattered under fm6?

--sd

If "Perform Auto-Enter Options..." was unchecked, lookups, serial #'s, modification dates, etc. would not change. This definitely isn't the issue.

I am looking more closely at the data and realizing that the lookup is happening every 25th record... which implies that imported records are committed 25 at a time? Can anyone corroborate?

The order of operations changed slightly after 6. It's hard to say exactly how; it has to do with the order and internal triggering of events, but some small things that worked in 6 no longer work. A new feature can help, which is to use an auto-enter calculation, and uncheck the [ ] Do not replace existing data; if that is appropriate.

Another more drastic, but reliable method is to do a Loop or Replace on all the imported records.

I'm guessing you do not have these self-related data fields in the data you're importing? Because if so you could just import them.

(P.S. I would love to see an in-depth explanation of the internal order of operations pertaining to lookups, calculations, auto-enter calculations, and Imports.)

Yes, even Auto-Enter Calcs with "Do Not Replace..." hasn't helped. I'v gone with the script, which is actually proving to be more efficient than the old method anyway...

Thanks!

But these selflookups, are used for what? - if it's for tunneling values are they an ancronism to maintain:

http://previews.filemakermagazine.com/videos/541/GraphRules_full.mov

I'd dare say not even when anchor buoying which by convention not utilizes bidirectionality, is such mechanisms hardly required any more.

The tough reply is your relational structure is not embracing the features the relations can convey by insisting on a set and forget migration. Have you studied the migration foundations whitepaper or are you just hoping for the best??

--sd