Property Access must assign to the property or use its value

[carlson_46]

Hi,
I created a windows form, then i have another menu kind of windows form to open other windows form. 2 menu button to divert to another windows form is working, only one is not working. I have tried creating a few windows form to test and all results the same. Below is the screenshot, please help. Thanks

[Maverickz]

sales_report_qnty does not appear to be a proper form. If it was then the .show() method would have auto-capitalized to .Show().
You may have to make backups of the related files, delete it and recreate the form and paste the code back in.

[jmcilhinney]

Check the Solution Explorer to see whether that class shows the correct Form icon. I'll wager that it doesn't. Someone solved an issue like this recently but I can't recall which thread it was. I think that, if you open the designer code file for that form and one that's working, you may well be able to see what's missing in the broken one. I think that's what the other person did.

[carlson_46]

Hi Guys,
As Far as i've checked, everything seems the same, i have deleted and created another windows form and still the same. Let me know if there is any other suggestions. Thanks

[techgnome]

What happens if you create an instance of that form and show it? Instead of using the default instance, create an explicit instance and see if that works.

-tg

[jmcilhinney]

What happens if you create an instance of that form and show it? Instead of using the default instance, create an explicit instance and see if that works.

-tg

That's a very good point. Have you, by any chance, added a constructor with one or more parameters to that form without also adding a parameterless constructor? If so then that form will have no default instance because a parameterless constructor is required to create a default instance.

[techgnome]

What I'm wondering is if there's a problem with the constructor/initialization of the form that prevents the default instance from being created, and so it isn't able to assign the property a value, which would result in the error above. On a side note, I wouldn't have different forms for what appears to be the same report, just with different parameters or groupings... I'd have a single report that could handle it all, but modify itself depending on the parameters. Then I'd simply show that form (or rather an instance of it) passing it the different parameters so it shows correctly ... but then again, I know diddly about the report and am simply going based on the code in the screenshot, I think I'll shaddup now...

-tg

[jmcilhinney]

What I'm wondering is if there's a problem with the constructor/initialization of the form that prevents the default instance from being created, and so it isn't able to assign the property a value, which would result in the error above.

What you're describing sounds like it would generate a run time error though, rather than a compilation error.

[FunkyDexter]

Just another straw to clutch at but is it possible you've accidentally removes the "inherits Form" line from the designer code?

[Inferrd]

Talking of straws....

What happens if you right click on the word show and select "Go To Definition" in the context menu? Does it take you to an actual Property definition.... or somewhere else?

[techgnome]

What you're describing sounds like it would generate a run time error though, rather than a compilation error.

You'd think so, and yet it wouldn't have been the weirdest thing I've seen in VS.

Talking of straws....

What happens if you right click on the word show and select "Go To Definition" in the context menu? Does it take you to an actual Property definition.... or somewhere else?

Actually, I now wonder if there is a property that's been added to the form called "Show" ... that would cause the compiler to get confused...

-tg

[Inferrd]

Actually, I now wonder if there is a property that's been added to the form called "Show" ... that would cause the compiler to get confused...

That's what I was thinking. A Property definition for show with a small s as seen in the attachment.

Creating a property named show should give a compiler warning, though warnings are easier to miss than errors.

Without the Property definition, "Go To Definition" takes me to the Object Browser in VS2010, and somewhere confusing I've never been before in VS2015.

[carlson_46]

Hi All,
Thanks for your reply, i found the solution. I just change the part below and it worked. Previously it was set as textbox, i changed it to the form name. Thanks

[jmcilhinney]

So, you're saying that you had a TextBox on the form containing the code with the same name as the form you want to open?

[carlson_46]

Hi,
No, the form name and text box not the same, but for some reason, (Im not sure what you call the bar up there) it defaults to textbox name, later i changed it and save, after that it was fine. Thanks

[jmcilhinney]

Hi,
No, the form name and text box not the same, but for some reason, (Im not sure what you call the bar up there) it defaults to textbox name, later i changed it and save, after that it was fine. Thanks

That doesn't actually make any sense but I guess it's a moot point as what you wanted to work is working and that's what matters.

[carlson_46]

Yup, as long it is working, Im Happy.