>>Michelle,
>>
>>You won't have a conflict with two forms opening the same table. It does check to see if it's already open. You'll need to decide whether or not to use private datasessions. If you do, you can have two forms using the same table each with its own record pointer. This is great if you need to open the same for twice.
>>
>>I think, but you can check it out, that VFP will look in the current directory if the table's not in the specified path. This can be a pain if you have a table in the specified path and in the current directory. If this is the case you may want to open the tables manually in your form's load event.

VFP looks FIRST at the hard-coded path which is saved in the data-environment. Second in the current directory and third in the path. This can cause major problems when you move an EXE from test to production directories.

>
>I don't think I'll need data sessions. At this point I can't conceive of a situation where I'd need to open the same form twice. But you never know. :)

Biggest problem isn't OPENING tables, but making sure form1 doesn't close tables that form2 needs. That's one VERY good reason to use private datasessions.


>What do people generally do for table management? Do you open them manually or put them in the data environment? I'm starting over from scratch, so I'm open to any ideas on the best way to do this.
>
>Thanks,

Michelle, you're PUTM. Do a search on the word 'datasession'. You'll come up with several recent threads that have discussed these options in detail. You'll probably get the most information that way.

HTH
Barbara