>>>>>>>>>>>>>>
In particular what are the side affects of changing a forms datasession from public to private. The application does
>use a few global variables, but the are thinks like userid, timeout for message boxes, etc (around 5 or 6).
>
>The forms are in two broad catagories:
>
>1. front end for reports where datasession is in the form not the report.
>
>2. data entery forms which may call other forms.
>
>The application was rewritten in VFP 5 (orignal was FPW 2.6)
>
>It needs to be moved to VFP 6 and eventually 7.
>>>>>>>>>>>>>>

Check out http://fox.wikis.com/wc.dll?Wiki~DataSession~VFP

>>>>>>>>>>>>>>
The application does use a few global variables, but the are thinks like userid, timeout for message boxes, etc (around 5 or 6)
>>>>>>>>>>>>>>

Public variables are a bad idea because they break encapsulation. Problems can creep up that are hard to debug.

Use properties in an application object instead. Could even be properties you add to _Screen

See also: http://fox.wikis.com/wc.dll?Wiki~PublicAndPrivateVariables~VFP