Only One Button code works on this form - troubleshoot help requested

[Micron]

I agree that one needs to learn to walk before trying to run but question if the percentage that never uses classes is that high. It would be my preference in some cases, over several TempVars or DLookups. Case in point is a project I developed at work that had but 2 classes - an email object and a user object. User object had several properties (FName, LName, EmplNo, etc.) and any time I wanted to use any of the 7 or so properties in code, they were all in one object.

The problem I see with the employee class here is that there is no initialize event so the object doesn't get created. Could be why the code won't compile but I don't know.

[Amyfb]

Are you absolutely sure? Look at the OnClick event property setting for your button. It definitely shows [embedded macro].

Attachment 46083

okay, here, in this one instance the book has me click the button to then get to the code builder. I now understand how this "embeds" the code but I thought it was all about the Form module where it was contained with other code.

my head is starting to spin a little here. guess i need to slow down a little.

[Amyfb]

I agree that one needs to learn to walk before trying to run.......
The problem I see with the employee class here is that there is no initialize event so the object doesn't get created. Could be why the code won't compile but I don't know.

I've just downloaded the files that go with the book, and am comparing their code with my code , line by line, to see if i can see why their file works and mine does not.
so far, I found one property without a Let statement on my code (that the book specifically said to omit.....smh) but i don't know if that's everything.

thanks for the input - you folks are a treasure !

[moke123]

I'm ready to toss this book in the trash - it's been a headache from page one. It's as if every other example is missing some little bit.
Does anyone have a recommendation for a solid workbook?

What book is it?

I would classify custom classes as rather advanced. It took me years before many of the concepts finally clicked.

[Micron]

the book has me click the button to then get to the code builder

Did you notice that there were 2 buttons? One is for macros, the other for code. If you set the db option as stated above you should only see the one with the ellipses (...) for code from then on. I think you might have to close and re-open db after setting the property for that setting to take affect.

[davegri]

@Micron

I agree that one needs to learn to walk before trying to run but question if the percentage that never uses classes is that high. It would be my preference in some cases, over several TempVars or DLookups. Case in point is a project I developed at work that had but 2 classes - an email object and a user object. User object had several properties (FName, LName, EmplNo, etc.) and any time I wanted to use any of the 7 or so properties in code, they were all in one object.

As an alternate to a class object, your User class object could easily have been a simple User Type. That would have allowed you to refer to the fields as .FName, .LName, .EmplNo anywhere in your code. The cat gets skinned again.

[isladogs]

As well as all the other unnecessary complications that others have mentioned, I also noticed it is based on a UserForm.
Whilst standard in Excel, these are unnecessary and only rarely used in Access.

[Amyfb]

I want to report back on the results of comparing my code to the digital file supplied as accompaniment to the book.
1. there was a missing Let statement for one property, and the book instructed to omit it. (thanks author!) I added the statement in.
2. all the code in the frmModule was in a completely different sequence than how it was in the book. (why author?) I rearranged the code to match.

AND NOW - it works as expected. But I don't know which of the two fixes I did was the one that worked or if it was a combo of both.

and, it works without a table, I guess because all we're asking it to do is populate the listbox!

The book in question is: Access 2019 Programming by Julitta Korol. I also have the Access 2019 Bible by Michael Alexander, but admit I didn't do many of the exercises in that book because - "running" looked like so much more fun than crawling.

thanks again for all the input folks!

[June7]

Order of procedures in module is irrelevant to performance.

[moke123]

Your book is instructing you to use custom classes. I would estimate that over 98% of Access developers do not ever code custom class modules. It's a very specialized niche, and in my opinion is never required, as the desired result can be accomplished via normal VBA code.

But Dave, you've got to agree they're fun!

[davegri]

But Dave, you've got to agree they're fun!

About as much fun as a severe sunburn.

[orange]

Amyfb,

If you are looking for tutorials on specific topics, I highly recommend these youtube series by

Steve Bishop
Richard Rost

Here are many articles and tutorials on Database Planning and Design and more.

[Welshgasman]

but admit I didn't do many of the exercises in that book because - "running" looked like so much more fun than crawling.

And you will soon have the bruises to prove it is not.

[ssanfu]

I would classify custom classes as rather advanced. It took me years before many of the concepts finally clicked.

Those concepts still hasn't clicked for me ....... (1 of many concepts)

[Micron]

@Micron


As an alternate to a class object, your User class object could easily have been a simple User Type. That would have allowed you to refer to the fields as .FName, .LName, .EmplNo anywhere in your code. The cat gets skinned again.

So that is better? Or is it just different?