If you have a field with a set of checkboxes and click two or more checkboxes, all the selected values are stored in the field, separated by returns.
Thus if you click "active" and "Pending", you will find either
depending on which check box you clicked first.
Thus, any expression that uses = to compare this to field to a specific value or a field storing one specific value will never be true.
You could use an expression with the FilterValues function, but I suggest an "old school" approach when using check boxes to filter a portal like this.
Currently, your portal's table is related to the layout's table in some sort of relationship such as:
LayoutTable::PrimaryKey = PortalTable::ForeignKey
Modify the relationship to be:
LayoutTable::PrimaryKey = PortalTable::ForeignKey AND
LayoutTable::GlobalField = PortalTable::Status
This will not need any scripting to refresh the portal nor is any portal filter required. THis relaitonship exploits the fact that if you have a list of values in a fields separated by returns, it will match to related records by any one value in the list. In the above example, selecting "active" and "pending" would mean that any record with "pending" OR "Active" in the status field will match to the GlobalField and appear in the portal.
Thnaks so much for the help! I hope you don't mind the trivial questions. For some reason the complicated logic and aspects of the program i can figure out, but the trivial things i can't. I make sure to search the web, documentation and forum as best i can before posting so i don't spam it, but sometimes i can't stumble across the answer. Thanks again.