If not using properties for the fields, I would have to find another way to pass the values to the BO. I guess one way is to populate XML and pass it. I will have to try it.
And thank you for the warning about VFP 6 bug.
>I would not have one property for each field. IMO, it limits your implementation too much.
>
>If you want the BO in a separate data session, I would definately use the session object. Be aware of a bug in VFP6. The session object uses the default data session by default, so you'll have to set it to a private session.
>
>>Maybe I did't explain myselft clearly. I was thinking of creating BO based on the form (but not data entry form) so that when data tables are opened within BO they would be handled in private session. And as you suggested, I would then instantiate the BO class in INIT of the data entry form. I thought that if I use a custom object as a base for BO class, the data would not be "encapsulated". But maybe I should rethink it.
>>The question I had in my mind, mostly, when I posted the message is if it is correct to create a property for every field of the table where the data will be saved.
>>Thank you so much for your input.
>>
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
