Hi everyone,

I've been developing a Members database and there are a lot of 1:many relationships. Most of the many tables show in a portal on the MEMBERS layout; this works great... Until I added a MEETINGS table.

Trouble #1

The Meetings layout is based on Members.

The portal is based on Meetings

I tried to filter the portal with Meetings::date=Meetings::gDate (gDate is global)

But, this was just 'wiggy' and unpredictable in it's outcome.

I tried (from reading the other posts), to put g_Date in Members and adding a relationship to Meetings::Date but that didn't work either. This begs the question "What good is portal sorting if I can't set Meetings::Date=Meetings::gDate and have it filter?"

I just want to be able to click the date popup (gDate), select date and have the portal reflect those records that have that date... I think there is something major I don't get here.

Trouble #2

Meetings::MemberName is a popup that is from a ValueList that is based on: Field -- Members::Name_LastFirst and.... despite the fact that this works in the other portals it does not work here. It just shows the field name.

grrrrrrrrrrr..... I think I have tried every conceivable permutation and combination and still can't 'get it'. I am off to bed.... Thanks for reading

This begs the question "What good is portal sorting if I can't set Meetings::Date=Meetings::gDate and have it filter?"

I don't think there is a connection between the two. Try adding a Refresh Window [Flush cached join results] script step upon modification of the global filter field. If you still can't make it work, post a file showing the problem.

I don't think there is a connection between the two. Try adding a Refresh Window [Flush cached join results] script step upon modification of the global filter field. If you still can't make it work, post a file showing the problem.

Right. The two are not related... For an explained reason, the value list problem resolved ... I have no idea why.

The bigger problem is not being able to FILTER the portal according to what is the g_Date global field....

The Meetings layout is based on Members.

The portal is based on Meetings

I tried to filter the portal with Meetings::date=Meetings::gDate (gDate is global)

But, this was just 'wiggy' and unpredictable in it's outcome.

I tried (from reading the other posts), to put g_Date in Members and adding a relationship to Meetings::Date but that didn't work either. This begs the question "What good is portal sorting if I can't set Meetings::Date=Meetings::gDate and have it filter?"

I'm having difficulty understanding your set-up.

If the layout is based on Members why is the portal based on Meetings "reverse" filtered by Meeting::Date=Meetings::gDate?

Wouldn't the filter be Members::gDate=Meetings::Date?