Difference in portal display client/server

[clausp]

Hi,

Anyone able to explain why there is a difference in appearance of some of my portals when serving them from FM Server 11 and running them directly in the client?

When served from FM Server nothing is shown in the portals though relation fields are valid, but running the same solution in the FMP 11 client shows all the data?

(The relations are unstored calculations with more values to multiple different fixed values).

?

Edited November 12, 2010 by Guest
The Topic: <a href="http://fmforums.com/forum/showtopic.php?tid/217673">Difference in portal display client/server</a> was moved from <a href="http://fmforums.com/forum/showforum.php?fid/32">Relationships</a> to <a href="http://fmforums.com/forum/showfor

[Vaughan]

Global fields behave differently in a served environment.

Not sure what you mean by "the relations are unstored calculations" because on the "child" side of the relation MUST be always stored for them to work.

[clausp]

Hi and thanks for reply.

Does global fields behave differently in any new way recently - or what do you mean?

My relation is a parent unstored calculation to a numerical field. No matter if i choose stored, unstored og global calculation, the relationship will not work when on the server. Locally its fine.

It is a many-to-many relationship where the calculated field has several values. Tried it both as a text and a numerical field. No success.

Global fields behave differently in a served environment.

Not sure what you mean by "the relations are unstored calculations" because on the "child" side of the relation MUST be always stored for them to work.

[bcooney]

Can you show us the data in the parent calc multikey? I'm wondering why it's unstored. Could the calc rely on a global?

[Vaughan]

Make sure the multi-key field is set to return text. It is a little bit sub-optimal matching text fields to number fields but as long as the key values are simple numbers (no alpha characters or leading zeros etc) then it works as expected.

The only other thing is screen refresh: are you committing the record and refreshing the window to update all the joins after making data changes?

[clausp]

Hi - and tx for the inputs.

The calculated parent field is a text field, that surely enough does contain the values to be used in the relation. And they do correpsond to the actual values on the child side. But nothing shows in the portal of the relation - not even first value of the relation (if placed outside the portal). Exept of course if i'm running the solution locally.

I'm not sure the actual calculation provides any further details - and it is quite complex and hold plugin commands, but it is listed below.

Notes:

All the fields from Usersession are globals.

Related child table is in a separate db-file.

Let ([

dt=Get(CurrentDate);

type="BETWEEN 0 AND 9 ";

date=W1_1; // W1_1 is a global containing a date

sql=

"SELECT "RowID" FROM Activities WHERE "& "(Task_AppointmentType "&

// Type of activity:

type&") "&

// Activity owner:

If(UserSession::ShowActivityForUserSelection ≠ "Alle" and UserSession::ShowActivityForUserSelection ≠ "";

"AND (Owner_s LIKE "&mFMb_DoSQL_Quote( "%"&UserSession::ShowActivityForUserSelection&"%")&" OR EmployeesAttached LIKE "&mFMb_DoSQL_Quote( "%"&UserSession::ShowActivityForUserSelection&"%")&") ";"")&

// Date of activity:

" AND (((AppStartDate_TaskStartDate <='"&Day(date)&"/"&Month(date)&"/"&Year(date)&"' AND AppDate_TaskDueDate >='"&Day(date)&"/"&Month(date)&"/"&Year(date)&"') AND InCalendar='Yes') OR

(AppDate_TaskDueDate ='"&Day(date)&"/"&Month(date)&"/"&Year(date)&"' AND InCalendar='Only enddate')) "&

// Project of activity:

If(UserSession::ShowactivityProjectID ≠ "All" and UserSession::ShowactivityProjectID ≠ "";

"AND cProjectID = '"&UserSession::ShowactivityProjectID&"' ";"")&

// Not private (visible for others)

"AND cViewableForCurrentuser = 1 "&

//Marketing related activity

If(not UserSession::ShowMarketingrelated activities;"AND MarketingrelatedActivity = 0 ";"")

];

doSql(sql;0)

)