One of the things that nails me is that my users have a tendancy to double click on the buttons. Either they get bored waiting and click again, or they think that nothing is happening and click or they don't understand that a single click is enough to trigger a button.

I usually make my first command in the click event of the button clear typeahead. that gets rid of any mouse clicks that are in the buffer.

I suppose that you should also give the user an obvious sign that you are busy. If you want to, you could play with the mouse pointer to make it show the busy hourglass, or you could just make the second line of code something like, wait window "Processing..." nowait and then the final line of code: wait clear.

Good luck man!

>Hi Evan,
>Well, i'm really just trying to implement the basic click event code for each button. i'm saving directly to a table. (i'll save the eccentric database tricks for after i'm a little more experienced)
>
>is the click event code all i need, and what problems might i encounter running a database this way?
>
>
>>>are there any good suggestions out there for a newbie trying to put save, cancel and exit buttons on a form?
>>
>>Which aspect are you having trouble with?