TABS, Tabs and tabs

[charl99]

Hi Bruce,

I keep bumping my head into TAB's.

So I know that I cannot Hide or Unhide or Include or Exclude these things dynamically YET.  This happens when the Form is initialised.

So, what is the possibility of making certain TABs Read Only and others not when I initialise the Form, say in Change mode when more information is required but the existing stuff cannot change (eg when certain things have to be approved before the user can proceed)?  Or a workaround, or something?

Thanks
Charl

Ja-ja-ja, tabs and a button to go to 'other places' on a Form is my 2 pet hates.  Sorry about that.

[Bruce]

>> a button to go to 'other places' on a Form

remind me what this is please?

[Bruce]

Hi Charl,

I think the key issue here is that the "tab" is not a "control". (The browser does not have sheet or tab controls). So you're seeing the "tab" as some sort of container, with properties like read-only or disabled or hidden, where changing the "container" changes the controls inside the container.

Of course this sort of metaphor can be "faked" to some extent - and support for at least hiding and unhiding the tabs should be coming soon.

To achieve what you want "now" you'd have to set the read-only etc properties for all the controls in the tab individually.

cheers
Bruce

[charl99]

Thanks, I was afraid you are going to say that, but your 'container' comparison is exactly as I see it or would like it to work.

>> a button to go to 'other places' on a Form

Some Forms are very long, so it would be nice to press a button to enter related information in a different place.  I guess you can compare it with a TAB but in another procedure. (give me some brandy with that TAB please.)

Or to do some complicated lookup stuff (if you need 3 criteria to bring back the right result the normal lookup don't work), or even just a memory form, obviously once you are allready in the Form.

Cheers

I'm off to the pub looking for some person to do all my Required_If conditions .

[Bruce]

With the new "popup form from other button" support in 5.19 this is now possible.

So what you'd have is a normal form (A), on the right table, with the "subset" of fields you want the user to see. Then create another procedure (B), a _memory form_, but which uses other fields from the same table.

Form A has a button, which calls Form (B) as a "popup". Because everything is session value based, form (B) is jsut setting session values, which should then be included when the SAVE button on form (A) is pressed.

I've not tried this layout yet myself, but it should work.

cheers
Bruce

[charl99]

Thanks, I'll give it a shot next time I need it, unfortunaely I have allready put all the crap on tabs

Cheers