experchange > solomon

solomonqueries (03-16-10, 07:30 PM)
Hello Everyone,

I am new to Solomon and would like to know the following:

According to the official Solomon documentation (p. 16 of
SAF_VisualBasicForApplications.PDF) the only click event available is
the click event for a button. Is this really the case?

My goal is to write a bit of code for the click event of an SSTab
control within the Inventory Item Lookup (10.210.00). So far my
attempts in creating such event code have been unsuccessful (ex:
Private Sub SSTab1_Click() ...).

Any information you can provide me is greatly appreciated.
Barry Flynn (03-16-10, 10:52 PM)
> the only click event available is
> the click event for a button. Is this really the case?

I think that might be true.
Offhand I can't think of any other objects that offer a Click Event that can
be used.

> My goal is to write a bit of code for the click event of an SSTab
> control within the Inventory Item Lookup (10.210.00).

My opinion is that if Solomon "doesn't want you to use that event", then you
should not use it.
In Solomon programming, you are always co existing with the Solomon kernel.
And in customization, you are also co-existing with the code in the host
program (10.210.00 in this case.)
If you start doing things "in a non-Solomon way", my feeling is that you
highten the risk of things not working in the future - for eaxmple after you
apply a service pack, or a hotfix, or upgrade to another version etc.

There may be places where doing undocumented things works and is "safe".
But its a risk you have to evaluate.

What are you wanting to do in the Tab's click event?
Perhaps there is an alternative way of achieving what you want to do?

Barry
solomonqueries (03-17-10, 02:56 PM)
Hello Barry,

Thanks for your help.

If you look at the standard Inventory Item Lookup there are two tabs :
Lookup by Description and Lookup by Attribute. In our customized
version of the screen we have "sub forms" that are open when you are
on the Lookup by Attribute tab. These "sub forms" allow the user to
specify additional filtering related to the Lookup by Attribute tab.
At the moment we have a button that allows the user to close the "sub
forms" when the user is on the Lookup by Description and another
button that allows the user to re-open the "sub forms" when the user
returns to the Lookup by Attribute tab.

> What are you wanting to do in the Tab's click event?
> Perhaps there is an alternative way of achieving what you want to do?


Basically, I would like to eliminate these buttons and use the tab's
click event to open and close the "sub forms" based on the tab that
the user has clicked on.

Thierry
Barry Flynn (03-17-10, 11:29 PM)
Thierry

Sorry - I can't think of a way of doing that.

My only real thought is a pretty silly one, which probably wouldn't be much
use.
You say (or imply) that the sub forms are not Modal.

If so, then one possible approach migjht be to provide a button on each Tab.
The purpose of each button is to switch tabs.
Its Click event would:-
- Do an ApplSetFocus to a field on the Tab that you want to go to. That
should make that Tab visible.
- Close & open sub forms as required.

That might (or might not) work.
I'm afraid that its about the best I can come up with.

Barry
solomonqueries (04-12-10, 10:28 PM)
Hello Barry,

Thank-you for your suggestion.

Kindest Regards,
Thierry
Similar Threads