Matt, Thanks for the explanation. I have a couple of follow-up questions if you don't mind. >A datasession is like a container. It contains a data environment >(explained below). You can have multiple data sessions open using multiple >forms and each data session cannot see the other. IOW, you can open the >same table, using the same alias, in multiple sessions and each instance of >the table can have the pointer at a different record. No instance of the >table affects another. It really eliminates some of the funky/creative >ways we've had to use aliases in the past. I take it then that there is only one data session per form. When you speak of multiple forms accessing the same file with the same alias not seeing each other, are you speaking about multiple instances of the app or a single app with multiple instances of the form? Or both? >A Form can use either the default datasession (1) or a private datasession >(property DataSession = 2). It's called private only because it's distinct >from the default session. If the form is still in memory (not released) >then its private data session (if defined) is available elsewhere, either >by issuing a SET DATASESSION TO or by setting another form's DataSessionID >to the DataSessionID of the form that created the datasession. (I hope >that wasn't too garbled, read it twice, that's what I did...lol) If I'm correct about one data session per form, what is the purpose of being able to have a default or a private data session? If you can have multiple data sessions per form, is there a limit to how many you can have? (Theoretical limit if not an absolute one) Thanks again for your help. Gary J. Sibio