Thanks, Claude. I played around last night trying to save the entire object to the Session object with varied results. FWIW, the problems were as follows:

1) After displaying the same page several times, the page would just cease loading

2) Weird behavior with Datasessions. Progressing from one web page to another resulted in the Datasession changing from 2 to 3, and I had to issue SET DATASESSION TO 2 in order to resume processing my tables. Once I checked and ALIAS() equaled "Session", so I'm not sure if this was the result of AVFP doing something behind the scenes.

Today, I've started saving the required properties to the Session object and this method seems to be working without problems.

Regards,
Dan

>Dan, because of the stateless nature of the web, you would probably have to save it to the Session object. (better to use the Session object than the SessionTable object). It should be easy enough to test, though, in a simple experiment. You may be able to save the entire object to the Session and you would need to see how that affects your app. If not able to save the entire object, then properties could definitely be saved to session.
>So, that user would be able to continually access those properties, but, other web users would not be able to access those properties(at least I don't think so). To do that sort of thing you'd need to use a table...