Don't Be THAT Guy

This one will be short. A few weeks ago I decided to update an old application I created a few years ago for a friend. It was created with Access 2002. The new version is in Access 2010 and it showcases a few 2010 specific features, as well as an updated table structure. I worked on it off and on over a couple of weeks. One night I was tweaking a form when Access threw an error, informing me it had experienced a problem and had to close. It allowed me to make a backup of the file and closed gracefully. That's not too uncommon, and most of the time recovery means finding the problem and correcting it before moving on.

Sometime I just want to be single, okay?

(Guest blog by Banana)

On the surface, it appears that VBA does not like it very much when you want to have a Singleton class. Whenever I write a class module, which is kind of rare given the general patterns in Access/VBA development, it's almost inevitable I want a Singleton. The only reason it's a class in first place is because I need some variables declared WithEvents. We can't do that in a standard module, so it has to be a class module.

No, Excel is NOT a Database

So, what's got my dander up today? I’m glad you asked.

Excel is NOT a database. You can't import Excel spreadsheets into Access and call that a database. You can't create "spreadsheets" directly in Access and call that a database. I wish more people understood that. It would make my blood pressure go down, probably down a lot.

New, New, New

Well. It's been an interesting 6 months.

New job.
New home.
New book project.
New Laptop (Rest in peace, worthy Dell Vostro).

So I'm long over due for a new blog post.

A work in Progress and 64 Bit VBA

I'm constantly amazed by the fact that this blog post remains near the top of the list of most viewed posts on my whole canon of 100+ posts.

Recently, I've found that there is at least one other first class post on the subject these days. Please read through my offering, then go visit Phillip Steifel at Code Kabinett.
============================================================
Recently, I revisited an Access demo I've been puttering around with for a while. In the process, I also had a great chance to take a stroll through the emerging information relating to 64 bit OS's and Access. The event that triggered this was moving this demo into Access 2010 (32 bit flavor) running on a 64 bit OS (Win 7).