Textbox enabling from Command button.

[Lensmeister]

Hi everyone,

I have a form with a number of textboxes on it. These are initially set ot enabled = no in their properties.

On the form is a command button named command26.

the event I want is that when the command is clicked, ALL the textboxes are then enabled (and the one checkbox is set to unchecked).

Therefore the logic path of this should be

Private Sub Command26_Click()
 
object.enable = true
object.checked = false
 
End Sub
 

So the code should read:

Private Sub Command26_Click()
 
Name.enabled = true
SignedDate.enabled = true
SignedFrom.enabled = True
AttheClub.checked = False
 
End Sub
 

But this has not worked. Can someone advise me where I have gone wrong please ?

Thanks in advance.

Lensmeister.

[Stewart Ross]

There is nothing obviously wrong from what you have shown us so far. Are you sure that the code is being run? There are no other syntax errors that would prevent the code module from running (simply checked by compiling the code)?

You can check to make sure that the event code is being run by setting a breakpoint in the last line of the sub. When the on-click event fires and the code is run the breakpoint will suspend code execution on the line concerned. If it does not suspend then the on-click event code is not actually associated with the on-click property of the control. This can happen if, for example, you change the name of a control and forget to change the name of any associated event handlers.

If the breakpoint does suspend the code it will give you the opportunity to check the status of each control's enabled property in the immediate window, by typing

? [controlname].enabled

or just by hovering the mouse over the relevant property in the VBA editor window.

By the way, you can check that you have the correct control names listed by using the shortcut Me property of the form followed by a period - this will list all object properties for the form, and if you then type the first letters of the control concerned you should see the control named in the list (with any spaces in its name replaced by underscores).

If you type, for example, Me.At then the Intellisense should show you all matches for that name - notably the AtTheClub control you mention. If it doesn't, the control would not appear to exist for that form. This may arise if the objects concerned are located on a subform instead of the mainform, or vice-versa.

-Stewart

[Lensmeister]

Thanks Stewart,

I will try this later.

Lensmeister.

[NeoPa]

One of your controls appears to be called Name. It is not recommended to reuse names with pre-existing meanings (such as Name). This is possibly not a problem for the compiler, but it's good policy, when this is deemed necessary (should never be so), to refer to them more explicitly, such as Me.Name. Name is one to avoid particularly, as it's clear now I type it that it already exists even as Me.Name. I suggest you consider making a rule for yourself never to use names like Name, or Date, or anything else which is likely to clash with something else.

[Lensmeister]

I will rename it (if it is a good idea)

txtName

'Name' is the title of the field in the Access DB. and I created the form with the wizard so it took that at the name of the control.

[NeoPa]

It certainly is a good idea. I'm always embarrassed to hear that a dodgy name was created by the wizards. Designed by the same company that tries to teach us how best we should organise our code. Ironic I suppose. Their advice is generally quite good mind you. Just their inability to follow it themselves is a bit of a giggle ;)

[missinglinq]

Stew mentioned the control AttheClub and I thought he'd hit on the snag in the code, but then he went somewhere else with it. But if you continue the line of thought, if you type in

Me.AttheClub.c

a dialog box will pop up listing all the Properties available for the control AttheClub that start with the letter "C." The first one, I believe, is ColumnHidden, which means that there is no Property named "checked."

So

AttheClub.checked = False

is incorrect syntax. What you mean to say is that the Value of AttheClub is False, No or 0 (Zero.) Since Value is the Default Property of a Checkbox, you can omit it and simply write it as

Me.AttheClub = False.

Don't know if this, along with the previous advice, about renaming your control and using Me. in order to take advantage of Intellisense, will solve all of your problem ("this has not worked" is not really very descriptive) but it will cause a error to pop, and the change is necessary if you want your checkbox to be unticked.

Welcome to Bytes!

Linq ;0)>

[Stewart Ross]

Lensmeister, you'd do well to take heed of the excellent points made by Linq, and also what NeoPa mentioned re names (wizard created or not!).

I suppose I was being a little oblique when I mentioned compiling your code. If you get into the habit of compiling any changes to your code the compiler will automatically catch as errors any references to non-existent object properties, at least if you refer explicitly to the objects concerned, as for example in

me.control.someproperty

My suspicion was that the code was not being executed at all, as if it was there should have been a run-time error when you tried to refer to a property such as checked that is not valid.

-Stewart

[Lensmeister]

Thanks guys the info has been noted and I will update the names of the controls.

I decided to take another tack on the enable = True/False etc.

I do need the controls on the form, but not able to be edited. Locked seemed like a better solution. Taking the info above I had a go at editing the code accordingly and now It is working well with the locked property being set to true on form load and when the command is clicked it changed the property of all the controls to unlocked.

Thanks a lot chaps :)

This is the best forum for help and info and I am learning more than I have on other forums. It's a lot more friendlier too.

Thanks again :)

[missinglinq]

Glad we could help, Lensmeister!!

Linq ;0)>

[Lensmeister]

Thanks Stewart,

I have it working now :)

[NeoPa]

I split the latest question away into its own thread (Sorry for the bad timing Stewart) - Select on CheckBox.