I was setting up a portal to filter data so that a user only his OWN, OPEN actions for ACTIVE projects (so 3 criteria).

My layout is based on table occurence MyStuff, the portal on its related table occurence ActionLog.

The relationship between both occurences is based on the following criteria:

MyStuff::Account (indexed txt with value user's accountname) = ActionLog::lu_Executor (stored/indexed calc txt with lookup of accountname of the user who needs to execute the action)

MyStuff::calc_Projectstatus (stored/indexed calc txt with value "active") = ActionLog::lu_Status (stored/indexed calc txt with lookup of value "active" or "closed" in related Projects database)

MyStuff::g_ActionStatus (global calc num with value 1) = ActionLog::Actionstatus (indexed numerical field with value 1, 0 or empty)

No idea what I'm doing wrong, but based on the above relationship, the portal remains EMPTY. When I remove the ActionStatus criterium, the portal works, but as soon as I add it again, the portal is empty.

What am I missing?

Edited September 23, 200817 yr by Guest

Additionally, when I try to perform a find in the portal, I get the message that "the operation cannot be completed because 1 or more of the relationships are invalid".

Strangely, I got the system to work this morning. I shut down the database for lunch, opened it again after lunch and it's once again not working!!!

Racking my brain over this one...

OK, now I'm really at a loss...

The database I'm using is running on FM Server. When I work on the live server database, I get the problems as stipulated above. However, when I work on a back-up copy of the database (stand-alone), everything works perfectly...

So I guess it's a server issue??? I haven't been working with FM Server very long, anyone have a clue for this one?

You probably have a file reference to a local file on your computer. So when it is served it can not find it but when you use it stand alone you have it. Double check your file references.

Thanks for your feedback, John! However, someone suggested that I change the definition of my field MyStuff::g_ActionStatus (global calc num with value 1) to a regular calc with value 1, and it works like a charm.

I would love to understand why that is, but for now I'm happy it works.

It seems I miunderstood your initial issue.

Global calcs have the same characteristics as normal global fields, including their traits when on a served solution.