Two things come to mind...
Are you using a multple files? Files don't share global variables.
How is the portal's table occurence related to the layout's table occurrence? Is the relationship valid? I've usually seen virtual list portals pulling records through a cartesian join, what is the ">" part of the relationship testing on?
1. Not using multiple files.
2. The relationship is definitely valid since it works properly when opened locally. The portal only fails when it's opened as a hosted solution...via FMS or hosted peer-to-peer.
The relationship joins a global count field to a record number field using a ≥ so that the portal only shows records that don't have blank values.
Also, forgot to thank you for your help.
It gets even weirder...if I flip the operator from ≥ to ≤ the portal works as expected in the hosted environment but FAILS in the local environment. I have to believe this is a problem with hosting the solution. Unless I'm missing something, a portal should not function one way locally and another hosted...especially one as simple as this.