[AccessD] enabled & disabled command buttons

ok, let me try that,  I was actually thinking about not letting a user
click on the button if it has been clicked in less then 15 hrs, could be a
good idea

> There are several ways to skin this cat, but OTTOMH, If this is a series
> of buttons that should behave in a normal tab order behavior you
> could...First enabled cmdButton2, then set the focus for cmdButton2 and
> disable cmdButton1 on the cmdButton1_click()
>
> -Francisco
> http://rcm.netfirms.com
> ----- Original Message -----
> From: <Oleg_123 at xuppa.com>
> To: <accessd at databaseadvisors.com>
> Sent: Friday, February 07, 2003 11:42 AM
> Subject: [AccessD] enabled & disabled command buttons
>
>
> : oops, I forgat to change the subject in my last post :((
> :
> : I have to do form where one button is enabled, rest are disabled. Once
> u : click on the first button, it becomes disabled, and the next one
> enabled. : I don't quite see how I can disable a button while its still
> got the focus...
>
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com



-----------------------------------------
Send a Xuppa Valentine to Your Sweetheart today!
http://www.xuppa.com/greet/