In NT8 i use a technique to save filters into a Sessionvalue that gets used in a related Browse where the filter is just set with the sessionvalue.
It has worked great for some time.
I am seeing more instances where the sessionvalue appears to get truncated, so my filter is truncated.
Its tricky to duplicate, it seems to work initially then as i change the sessionvalue the problem can occur.
(it might be aggravated by the serverstate saves!? as i see it more when i am testing)
in 9.06 I noticed this in version history
Fix: Session Values could be not-updated if value changed from very short to very long
Bruce could you shed some light on how long this issue was present - was it just new in 9 or was the issue pre-existing, as it smells similar to my experience. Might some variation exist in NT8? whats very long vs very short?
Today, I have taken to deleting the session value before setting it, as my work-around which I think helps for my specific cases, time will tell., but obviously session values are used all over the place...
I am posed to update this to NT9, but for various reasons, not yet. I am wondering if there was a Fix that could be retrofitted for NT8
tia
poul