>
>I have no further ideas, what could be going awry.
>>
>>However, I would recommend that all forms, and especially forms that work with data, use a private DataSession, and open their own tables (either in the DataEnvironment, or in the Form.Load() Event). This should not be too much trouble, even for a "quick-and-dirty" form.>
>Thanks for your time Hilmar. I've always avoided the DataSession and preferred to open the tables in the calling code. Maybe not the most proper OOP, but it has worked for me. I just have not figured out what's wrong with this one. I'll try using the Form.Load() event.
I use both the DataEnvironment and Load(); before VFP 8, I think it is, Load() is the only option for a form that is saved as a class.
The advantage of the private datasession is that forms will hardly ever conflict one with another; this makes it quite easy to design a system where you have several forms open at the same time.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
