v4.1 to 5.0 and 5.5 Conversion Bug

[Tommy Z]

I am frustrated and on a deadline to finish some work. I hope someone will be able to help me urgently.

I have a seriously complex solution in v4.1. When I convert to either 5.0 or 5.5 (same problem occurs on both Mac OS 9.2.1 and Windows ME) one of my scripts that takes me to a related record from a portal to and displayed that record in another file stops working. The record displayed at the end of the script is always the first record in the portal.

Has anyone else experienced this apparent anomaly? Does anyone have a fix?

Thank you in advance for your answers.

[BobWeaver]

Can you show us what your script looks like?

[MeltDown]

I know there are differences in how FMPro 4.0 and 5.0 handle portal records in CDML, but I haven't really worked with portals much in FMPro 4.0 ...you may want to look at the FMPro site to see if there is anything related to your specific problem.

ALSO, If you haven't already done so, check to make sure the sub-script is actually pointed at the correct database in the correct folder on the correct computer. We had a similar problem several months ago with scripts working incorrectly when we replaced one of our databases in a complex solution with a modified copy of the same database from our 'test' server. The relationships, sub-scripts, etc. looked correct, but we finally figured out that the sub-script was actually going to a really old version of the database on a completely different server. We fixed the problem by going through the entire solution and fully re-setting every relationship, portal, value-list, and script-step that called up a script from a different database (they may look ok, but if you don't actually re-set them they can stay pointed at old directories or even other servers). It didn't really take as long as we thought it would, and was well worth the effort. It could be that some of your relationships are somehow getting 'confused' during the conversion process.

(We shoulda sent our FMPro databases to marriage counseling!)

HTH!

Merry Christmas!

[Steven H. Blackwell]

quote:

---

Originally posted by Tommy Z:

I am frustrated and on a deadline to finish some work. I hope someone will be able to help me urgently.

I have a seriously complex solution in v4.1. When I convert to either 5.0 or 5.5 (same problem occurs on both Mac OS 9.2.1 and Windows ME) one of my scripts that takes me to a related record from a portal to and displayed that record in another file stops working. The record displayed at the end of the script is always the first record in the portal.

Has anyone else experienced this apparent anomaly? Does anyone have a fix?

Thank you in advance for your answers.

---

Completely reliable portal record to related record navigation, especially from a button in a portal row, requires seizing the record ID (not the foreign key) of the record in the portal row, setting that ID into a global field in the parent file, then navigating to the related file based on a second relationship with the global as the foreign key in the parent file and the record ID as the primary key in the related file. This means that there must be a field in the file, a stored (not unstored) calculation set to equal Status(CurrentRecordID). Do NOT use this for any other purpose such as a key.

HTH

Old Advance Man

[BruceJ]

I ran into the same problem and ended up out of despiration randomly trying different arrangements.

The solution - don't ask me why - was to break up the main script.

Main:ScriptA

from a button on the portal row:

GoTo Related Record

Perform ScriptB

Main:ScriptB

Perform External ScriptC

SecondFile:ScriptC

GoTo Layout X

It was adding the ScriptB which I would have normally just written as a second line of ScriptA after the GoTo Related Record command.

I don't know why, but it worked.

[bbaliner]

Old,

Forgive me for butting in on your conversation, but why is it necessary to go through this? I mean using this second relationship instead of the regular PK to FK relationship.

If the relationship is not valid no record will be seen in the portal anyhow, and if it is valid, then simple "Go to related recored" will suffice. Please clerify.

Thanks

[BruceJ]

Bike -

The problem is when you have a portal with serveral records displayed.

You create a button on each row of the protal to go to the related record.

If you click on the button on record X in the protal you should go to record X right?

Not so for some odd reason, you go first related record in the portal. Strange.

I haven't noticed this while "converting" from 4 to 5, but I had it in a fresh new file I created from scratch in 5.