Hi Steven,

Have you considered creating an object, which instantiates right after you confirm that your user is valid, and storing the values you require in that object as either individual properties or values in an array property of that object?

This would then allow you to query this object from *anywhere* in your app, without worrying about whether your DE tables were open or closed. You could either use a Session object, which would keep this data --completely-- separate from your DE, or you could use a lightweight object like Line or Custom.

Looking forward, VFP 8 will help in things like this with its new Empty class/object.

HTH.

>I have a table that holds data for each user(password,name,email address, etc.) When a user starts the application they type in a password which either lets them continue if they are vaild users or the app goes no further if it can't find the password they entered.
>
>My design question is this. I need all the peices of data on the logged on user at various stages in my app to verify which functions are open to them since authoriy varies between users. Do I create a cursor based on the user after the password is verified and use the cursor results throughout my app? Or do I set up Public varibles based on the cursor results?
>
>Whats the best way to handle this? One note is at some points in my app I push data to remote tables. When this happens I have to close my tables in the DE and then open them again. Won't this kill my cursor?