Re: Unload - Need advice - Code still running

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Bob O`Bob (filterbob_at_yahoogroups.com)
Date: 03/08/04 

Date: Mon, 08 Mar 2004 11:13:56 -0800

Andrew Dunn wrote:
>
> resent !

Resent?

>
> "Andrew Dunn" <andrewd@cclXXXmenzies.com> wrote in message news:...
> > Bob ~ Do I sense a touch of sarcasm ?

Do I detect a touch of resentment? <vbg>

> >
> > User needs to select a bank account in order to enter statement details.
> > At any point, they can escape out of the program and return later to enter
> > more details.
> >
> > The first time they select an account, they will need to enter some
> > additional details - ie Openning / Closing Balance.
> > It is not neccessary to re-enter this information on subsequent entries.
> >
> > I just though that if the user selects a bank account from a combo list and
> > has already filled in the additional details, I would like the program to
> > take them straight to the data entry screens.
> >
> > Is that unreasonable in a GUI environment ?

I think so.

> >
> > I thought the natural point to do this was during the validate event as that
> > was when I was checking the account.
> >
> > I am only trying to unload a small sub-form.

Seems like a reasonable place to expect it; I just didn't have enough detail before,
or maybe it was just that I had a hard time following along with the particular way
it was described (I long ago accepted that different people have different communication
styles and sometimes there's difficult starting period)

I'm largely confused because as I recall, the Validate events don't even happen
until the user at least attempts to move focus off of the control. I was thinking
from your initial description that the click event might be a better choice.
In any case, I'm {partially) aware of there being several unusual issues surrounding
the events of comboboxes, since they go through some invisible gyrations to set up
and tear down child windows, and sometimes what doesn't work within one event procedure
will work from within another, or sometimes you use a trick like creating a timer just
to get an asynchronous action to happen after the event closes.

I think we're in agrement that adding a button may cause unnecessary work for the user,
and that's almost always something to avoid.

        Bob 

-- 
looking for work again  <http://obob.com/bob/resume/>
Quantcast