Error on command button wizard

[jcor]

Hi,


I believe it's kind a newbie question.

When I try to use to wizard to create a command button to open a form, in the end of the wizard I get this error.
"Method 'HyperlinkSubAddress' of object '_CommandButton' failed"

Anyone know what is the problem here? I used to create this buttons with no problem, but now (for something I did, probably) can't do this anymore.

Thanks in advance,

Jcor

[orange]

Tell us more of the specifics of the click event for the button. (show the click event code)
Give us a description of the context -- is this for a web application?

[jcor]

Hi, sorry for the lack of context.

It isn't any webapp, I just designed a form (that is my entry form) with several buttons and each of them call other forms.
I don't have any code by myself, the wizard is supposed to implement the call of the form.
What I do is Insert button > Form Operations > Open Form > select my form > next > next > select the button name > Finish

The weird thing is that "before", yesterday or something, I was able to do this.

I found something, don't know if has anything to do with it, but in my code (VBA) window, in references I have a name (Database4 that is differente of my application name (Database 0605). Maybe is ome inconsistency here?

Thanks for any help,

regards,

jcor

[orange]

I don't understand how the message fits the situation.
"Method 'HyperlinkSubAddress' of object '_CommandButton' failed" sounds like some other properties or setting must be involved.

[Missinglinq]

It's not really unheard of for error messages in Access 'not fitting the situation!'

Also, although we usually think of Forms, and even entire Databases, when we speak of corruption, Controls, such as Command Buttons and Comboboxes, can and do become corrupted, and seem particularly susceptible to this during app development. The test/cure for this is short and simple...delete and then re-create the Control.

If a new button repeats the error, you'd have to think about the Command Button Wizard, itself, being corrupted.

Linq ;0)>

[orange]

Yes Linq you are correct. We've all been through those partial corruption special features %x##@#!.
Very likely some corruption in the making.

[Missinglinq]

Hopefully just that button, and not the Wizard!

[jcor]

Hello, I tried several times, off course, and the error remains

I'll create a new app from the scratch with the same functionality an will let you guys know if the issue remains. I believe it will not.

regards,

jcor