Hi Victor, and thanks!

I realized about the class too late.

From what you're saying I have a feeling that my tiers are getting somewhat tied up.

I'm working on a form that will alow the user to enter a record in table "A" only if a number of conditions are met one after the other.

The form that holds the "keys" has a few fields and button that the user must fill and click sequentially. This form doesn't have a business object. No data there. But as each "lock" is opened (via its own form WITH a busobj), some data of the lock that was just opened is supposed to be passed to the next and be saved by it as the user enters data in the new form.

I just tried in the click method of a "save" button, to add code like this:

v_view.unlock_value = thisform.oCallingform.nUnlockVal

It didn't work. I got errors.

However if I put a textbox on the form, initialize it to thisform.oCallingForm.nUnlockVal, tie its data source to v_view (the view that feeds the busObj), and make it invisible (the user doens't need to see this number), it works.

Does this mean that every time I want to update a table from a form I have to do it using hidden textboxes on the form?

There has to be something I'm missing... :(

Thanks!

Alex


>I just got back from taking the Kevin's course for the second time. I understood it alot better this time around. I too had questions like you had about being OOPishly correct. According to Kevin the basic rule of thumb is to keep Tier 1 (user interface) separate from Tier 2 (bizness classes) separate from Tier 3 (data). However, when using a friendly environment in Tier 1 you can basically do almost anything you want as long as it doesn't interfere with Tier 2 and 3. I wouldn't go as far as making stupid code on Tier 1 but I would think that using your code as you presented here would okay so long as you don't bind Tier 1 and 2 or 3 for that matter....