Why doesn't this work? (1 Viewer)

Whenever I click on button6 I expect two things to happen:
1) my global variable gets set to "COMMUNITY"
2) the frmCommunity opens

As it stands the form opens just fine, but my global variable never gets set to "COMMUNITY", what's going on here?

Respectfully,
-Gary

Should it not be..
Or am I missing something?

I tried that, but it didn't work... it said "Object required"

This worked though:


Thanks for the response, it made me think about when I need to set the variable.

Normally you use DoCmd.OpenForm to open the Form. I have not used Load method before. Is it possible you could explain what is that you are doing so I can learn?

I use docmd.open form... when I code in MS Access... but it doesn't seem to work with Excel... or maybe I don't have some reference loaded... IDK...

FYI: I've coded many years in VBA in MS Access, but I have only been coding in excel for a very short time... When I looked up how to open forms in Excel, that's the code I found. It worked, so i didn't worry about why, I just used it.

Maybe someone smarter in both venues can tell us why.

Regards,
Gary

This is old but may help

http://www.tek-tips.com/viewthread.cfm?qid=156798

Brian

A UserForm is a Class module provided by VBA. In the VBA IDE in Excel, if you right click on the Project Explorer window and hover your mouse over Insert, you can add a UserForm to your Excel VBA Project. Whan you add a UserForm object, it shows up in the object browser as a Private Class in the VBA Project referenced by your Excel file. A VBA.UserForm is a lot like an Access.Form, but a UserForm can't be bound to data and doesn't have a RecordSource property.

Access is actually a weird amalgam of object models. Access itself only really provides Form and Report objects, and the controls you can put on them. The Database is provided by Jet, and usually people use DAO to read and write to and from Jet tables, but it's DAO that provides the TabelDef, QueryDef, and Recordset objects we're familliar with. And CurrentDb is Access exposing a DAO.Database. File dialogs are from the Office object model. And all programming modules are provided by VBA.

When you look at the navigation pane and see all your tables and queries, forms and reports, it's actually amazing the diverse programming chunks that make that possible, and make it look like one product.

But yeah, UserForm is VBA. DoCmd and Form are Access.

Thanks Mark, until your reply came through. I did not notice this thread was in the Excel section. Well I have learnt something today ! Makes more sense now !