Go to Related Record bug?

[raymanj]

Is this a known bug with the "Go to Related Record" script step in FM 7?

Every time I use the script step "Go to Related Record" it shows <unknown> for the layout.:

Go to Related Record [ From table: "{Inventory}"; Using layout: <unknown> ] [ Show only related records; New window ]

Even though I can set the layout in the "Show record using layout" menu of the script step. I click OK to dismiss the dialog box. It shows <unknown> for the layout, so I click OK and save the script and run it. The script runs fine it goes to the the correct layout. I come back to the script and it still shows <unknown> for the layout.

I save all my scripts as a PDF doc and do a search for "unknown". I find hundreds of <unknown> and they are all in a "Go to Related Record" script step.

So do others see this same error? Is it just me? Is it a corrupted file or a bad install of FM 7?

Mac OSX 10.3

FM 7.0v3

[-Queue-]

I thought this was fixed in v3. Did you add the GTRR steps in v3 or previous ones? If previous ones, respecify the layout and see if that helps.

[raymanj]

Did you add the GTRR steps in v3 or previous ones? If previous ones, respecify the layout and see if that helps.

Some of the GTRRs were made in earlier versions of FM 7. This file is not a conversion from FM 6 and below.

I tried to re-specify the layout in a few GTRRs and nothing seemed to stick. While doing this I decided to change the layouts to <Current Layout> and it stuck. So I tried "Layout Name by Calculation" and "Layout Number by Calculation" and they stuck too, but none of the other layouts would stick which were made by me.

Next test, I recovered the file to see if this would fix it, nothing. Same symptoms. Then I created a brand new file. This worked. No more Using Layout: <unknown>.

So now I am stuck with a file that is a big project. I have been working on for a few months now and it is full of unknown error on each GTRR.

I am thinking if I can unistall FM and reinstall it, this might fix the problem.

Can anyone reproduce this error? It is a pre 7.0v3 file.

Is there anyway to repair the file?

[-Queue-]

Bummer. Well, even though it shows <unknown>, it does save it and the step works. So if you can live with it for the time being, since it doesn't cause any problems, maybe FM will have a fix for it eventually.

[raymanj]

Well I reinstalled Filemaker and no go.

Does anyone know of a product that can copy an entire FM file's contents (field definitions, layouts, scripts, value list, file ref, etc) into a another file, preferably a new blank file.

This is a massive file. I have created. I could maybe live with it for no but in the future, looking for bugs in my scripts will be hell. My tried and trusted way of saving my scripts into a PDF and doing searches has been wounded.

I am at a cross roads. I am only half way finished with this project. I have to decide to start all over and copy everything by hand or keep the file and let these GTRR bugs multiple.

This is probably the biggest disadvantage of FIlemaker. Once you start a file you are stuck with it. Filemaker really needs to make a way to transfer file definitions from to another.

[raymanj]

I have figured out what exactly is causing this Go To Related Record (GTRR) bug. But I need someone to verify it by recreating the bug themselves.

GTRR Bug:

At first I thought it affected all instances of the GTRR script step in any file, but when created new files it did not appear. While I was working with this new file the bug reappeared a few days later. I noticed it showed up on GTRR steps that involved table occurrences pointing to tables that were out side the current file.

So now I think this GTRR bug only appears when the GTRR includes a TO pointing to another file containing the table. This may be a another bug regarding referenced files and FM 7.

I have attached a sample file to see if you guys can see it on your computer. Then I need you to create a new file to see if it effects all newly created files in FM 7.

Any feed back is needed.

Samples.zip

[Fenton]

This is a known bug. I've seen it discussed on another list. Basically, the step works fine, but it doesn't read right. I imagine FileMaker will fix it. Then probably all your visible "errors" will go away without you doing anything. Hopefully.