Flush cached join results - variable results!

[IdealData]

I'm mid-process developing a system comprising around 60+ tables with around 250+ TOs. Some of the layouts feature multiple filtered portals on separate TABS - these are the ones giving the problem.

The refresh window command (by hand or script) doesn't always reset the cached results for all the related tables on the separate TABS even though they are on the same window - there are 7 TABS, each with it's own portal from a TO. I'm simply doing:

Go to Layout

Refresh Window [Flush chached join results]

This does NOT happen when using the file single-user, but the caching problems occur when opening the file from a hosted point, either FMS or FMP.

My first attempt to overcome the problem was to go to each TAB in the layout and refresh window - this worked, albeit a little slow.

Finally I've amended my script to deliberately set a new value to one of the filters for each TAB and a single Refresh Window command - which works.

[color:red]This is worrying that I should get different results between single user and hosted, but worse that the Refresh Window yields inconsistent results.

I'm on FM9/FMS9 (Mac) and I haven't tested in FM10 - if you know of a better work around then please advise and hopefully someone at FMI is also listening.

Thanks

Edited December 13, 2009 by Guest

[Steven H. Blackwell]

As a general rule the "flush" steps work on the local copy of the file. They do not operate on the hosted copy on FIleMaker Server.

However, your copy of FIleMaker Pro on the workstation is in constant communication with FileMaker Server and you should be receiving updates of records and of join results. They discussed these processes at the Under the Hood session at the 2009 Devcon.

Steven

[IdealData]

Thanks Steven.

I understand what the flushing is and appreciate that it works locally but my results differ with what is claimed. My portals are based on globals, which are also work station specific, so no activity by anyone else can influence those.

My portals display invalid results at first start up, but once flushed seem to work correctly.

Sadly I couldn't get to Devcon 2009 so if there's any published material from "Under the Hood" a pointer would be appreciated.

[Steven H. Blackwell]

How are the globals set?

Steven

[Wim Decorte]

How deep are the related fields you're showing? How many hops away from the anchor?

[IdealData]

The globals are initialised at start up - thereafter in the hands of the user.