VBA and Access are horrific

[shurgs]

[rant]
I've programmed in many languages in my time and used many front-ends and I can honestly say I've never in my life come accross something that fails so hard.

For everything you make Access finds someway to break two other, completely unrelated things. It's like trying to wade through a pool of treacle wearing a gorilla suit whilst being stung by bees.

The code behind it must literally be made of poo. It's like Bill Gates took a big old dump on a piece of paper, smeared it about and then tried put the crap (1) and gaps (0) into Binary and then use that as the source code for Access.

Infact, without the help of other forumees here at Access World, I would have shot myself long before now. So what I'm trying to say, is 'Thank you'.
[/rant]

*Bang*

 

[The_Doc_Man]

You know, there are times I've felt that way. Usually because I had preconceived notions from other programming languages and environments.

[rant]
To my way of thinking, and this is just one man's not-often-humble opinion, a lot of the headaches caused by VBA/Access would be solved if the Access objects were in fact truly object oriented.

I cannot even begin to tell you how often I've done something innocuous that just all at once jumped up to bite my toches hard. On inspection, I discovered it was because something was unbound, so one of the properties I thought it might have was in fact not there. Yet when I did tests on object types, the object was of a type that should have had those properties. What they don't let you see is the inherited properties that come from being BOUND vs. UNBOUND. In other words, the object property collections can be inconsistent for something so simple as two text boxes. Yet when I open the object browser, it doesn't indicate dependencies on bound vs unbound situations.

I have usually programmed my way out those paper bags, but the need to do so is what irks me.
[/rant]