Wrapping controls WithEvents in classes

I think I might change my way of working, and just work through the book, BUT, go to your DB to review the code, instead of creating the demo dB, as too much is changing all the time?
So as long as the book matches to the db, that process should be more reliable?
 
This strikes me as being somewhat akin to signing up for the Microsoft Office beta channel. ;) You get to see the newest stuff all the time, but sometimes you're not quite ready for it.

Seriously, though, feedback is tremendously important to a work in process like this.
 
This strikes me as being somewhat akin to signing up for the Microsoft Office beta channel. ;) You get to see the newest stuff all the time, but sometimes you're not quite ready for it.

Seriously, though, feedback is tremendously important to a work in process like this.
Yes, and @Gasman has been a real trooper struggling to keep me in line.
 
I think I might change my way of working, and just work through the book, BUT, go to your DB to review the code, instead of creating the demo dB, as too much is changing all the time?
So as long as the book matches to the db, that process should be more reliable?
I just spent all morning out in the demo database itself fixing naming convention errors, and adding a pCtlName property in every control wrapper class. I pushed those back into the book, though only 4 of the dozens of controls / control classes from the demo database have made it into the book so far. The nice part of doing such in the db is that a compile instantly tells me when my cut and paste has introduced an issue. I can just fix it. The book doesn't give me this feedback.
 
This strikes me as being somewhat akin to signing up for the Microsoft Office beta channel. ;) You get to see the newest stuff all the time, but sometimes you're not quite ready for it.

Seriously, though, feedback is tremendously important to a work in process like this.
It strikes me as signing up to rewrite the demo database included in Access. That had to be even worse. And sometimes it is not ready to be seen?
 
It strikes me as signing up to rewrite the demo database included in Access. That had to be even worse. And sometimes it is not ready to be seen?
And now I'm doing it in PowerApps too. :rolleyes:

It's going to be ready to be seen in about <mumbled> months.
 
LOL, going back and reading my own blog posts from 2013 is interesting. I was 12 years closer to my old work back then...:geek:
 

Users who are viewing this thread

Back
Top Bottom