Select Command One Time

goaksmith

Registered User.
Local time
Today, 03:51
Joined
Jul 31, 2002
Messages
74
I have a main form called frmClientData. On this form there is a command button that opens another form called frmOrderData. What the frmOrderData does it add a new order to the database for processing. What I want to happen is that after you click this command button once it becomes unavailable. The reason being is that the users make mistakes on their order and instead of editing the entry they create a new one. This creates lots of duplicate entries. By controling their ability to only add an order one time I am hoping to eliminate this problem. Is there any way that this could be accomplished? Thanks in advance for your help.
 
You can enable/disable the buttons.

Me.YourButton.Enabled = False

Also, You need to have an event that will enable the button.

HTH
 
Are you sure that's what you really want?

I tend to think you'd be better off by adding frmOrderData as a subform on frmClientData. If the relationships are right, then your users could see the faulty order, and make the corrections easily.
 
There is a subform that shows the orders. The problem is that they overlook this and add a new order anyways. You would think if they see their error they would fix it, but they don't they add a new one. I am trying to dummy proof this as much as possible.
 
Why use a button to add an order when you have the order subform available? Can't they just go to the subform and add a new record?
 
The subform is basically a summary of the order. Not all the fields are included. There are many more fields on the Add form that are not included in the subform. It is setup in this manner because their old system was setup like this. And they want to keep it as similar as they can. This is probably a bad reason. But they figure if people can't even learn to edit a record instead of adding a new record when they have a change that they won't be able to figure out a whole new way of doing things. The users aren't very techonologically savy.
 

Users who are viewing this thread

Back
Top Bottom