Unusual file behavior, maybe a bug

[kmhappel]

I have been building a version of a workflow management tool and have experienced some odd behavior, I was able to recreate it for the technical support people but they have not come back with an answer.

The behavior involves the portal relationship manager. When creating a script with a GoToRelatedRecord command, the relationhip manager asks for the relationship and then normally provides a list of layouts that match that relationship. After choosing the layout, the script step reads GoToRelatedRecord [show only related records; From table: "table_occurance_name"; Using layout: "layout_name" ( table_occurance_name )]

The unexpected behavior is:

1.) a final script notice of < unknown layout > when choosing a layout offerred as correct and, in fact, bound to the desired table occurance,

2.) incorrect binding with both the "layout name" and the( table_occurance_name ) being incorrect and being different than those chosen,

3.) after this symptom, many relation dependent script actions caused alerts of the type, "this action cannot be taken because the target is not related."

The actions that caused this behavior followed the creation of separate data and layout files and their linking to allow data and structure partitioning during upgrades. In version six this was no problem when each table was in one file. The current problem seems to be worst when the relational structure is modelled in multiple files, each having multiple table occurances of the same tables. Furthermore, it is transmitted to new databases in file copies, parts of data imports and imported layout elements so it seems to involve some kind of file and element corruption.

I went back to a developmental prototype where everything was in one file and have started to experience degredation that I believe is the onset of this corruption again ( the field definition tool is starting to refuse to acknowledge new global fields as global.

One thought I am pursuing is that there could be a limit or maximum number of global fields allowed and that exceeding it starts a gentle but persistent degradation.

Has anyone experienced this? Does anyone know how to fix it? I am trying all the advice on the site for fixing corrupt files. If I find a fix or the tech support people call back, I'll post an update.

Thank one and all in advance...

Edited September 9, 2005 by Guest

[comment]

I recall 2 or 3 threads here discussing the problem - you can find them by searching for +unknown +layout. IIRC, all the reports referred to a cosmetic problem - the scripts functioned properly.

At the time, I have managed to reproduce the problem, and here too, only the display in ScriptMaker was affected. You may have some additional problem/s, e.g. invalid file references, with this bug combining to cloud the issue.