Another Access 2007 Issue - Default grouping of objects on report and how the heck do you ungroup?

November 18th, 2008

Created a default report (I hate the lack of control you have on default reports!  Where are my old wizards that I’ve loved over the past 10 years?  Arrrggghhhh!!!!!).  Then started to modify the controls that were pre-populated on the screen.  Started by deleting undesirable controls.  All the controls to the right slid to the right!  Why the heck did this happen?  Not sure I like that.  What if I were reserving the deleted space for something else (which I was)?  Frustrating but let’s move on…

So I copied / pasted a label and text box (choosing both like a good little Access developer) and WhamO!  New controls just pasted are under the old controls!  Header & Detail section has bee expanded to accomodate.  Now I’ve got to move the new label individually, then the new control individually, then resize the header then resize the detail.  What a pain!  I realize the old way was flawed (pasting directly on top of the copied controls), but why this new solution of copying below?  How about still on top but slightly to the right to indicated the new controls are ’slightly’ on top of the old?  How much more convenient would that be!!!!!!  But wait, it gets worse…

Now I can’t even move my new controls!  There some sort of grouping issue going on so I need to ungroup.  Oh Lord!  I feel a headache coming on ’cause I’m sure they’ve moved the grouping/ungrouping process.  Sure enough, 5 minutes of searching reveals nothing (Another 5 minutes of my life gone done the tubes due to Access 2007.  Arrrggghhhh!!!!!!  What idiot at Microsoft has done this to us!)

So I get one of my other developers to come over and help.  Apparently she’s encountered this frustration previously and knows how to solve.  She right clicks the grouped controls scrolls down to Layout and chooses ‘Remove’.  That’s not intuitive, now is it?  How about giving us a choice to ‘Remove Grouping’?  would that be so difficult?  Idiocy!!!!!!!

Another Access 2007 Issue - Back Color values not working in code…

November 18th, 2008
I continue to be disappointed with Access 2007 from a Developer’s point of view.  Here is my most recent issue:

I’m attempting to set the backcolor property of a text box control using the ‘On Format’ event property of a report’s detail section.  I’ve been doing this sort of stuff for 10 years.

I want the backcolor to be green.  When setting this property from the ‘…’ choice in properties, the resulting value is ‘#22B14C’.  Note that I’m totally surprised by such a bizarre value as I’ve only gotten Long Integer values in the past.

Well, when I go to code to set the backcolor value:  txtConditional.backcolor = #22B14C, I get an error indicating that value can’t begin with a ‘#’ sign.  So I go ahead and wrap the value in double quotes: “#22B14C”.  I don’t get an error in code.

I choose the ‘View’ choice in the upper left hand corner of the report’s design view and it previews successfully.  Some of my rows are green, and some are red.  However, when I go to ‘print preview’ (btw, what the heck is the ‘View’ choice for, then?) I get an error telling me that the “#22B14C” value is incorrect.

Well that’s just great!  So now, I’ve got to go Google and figure out how to properly set this value.

 Conclusion:  Microsoft changed everything around like item above, and didn’t test, and didn’t take into account the thousands of experienced Access Developers.  More to come!

Jack Jaeger

President Data Control, LLC and

15 year Access Veteran

Working for UVA soon?

November 18th, 2008
Hey, just had my first meeting with a University of Virginia manager than needs an Access database built.  She’s got the process flow mapped out, the data structure mapped out, and now just needs the database built.

I asked her how she ‘found’ us, and she said ‘Craigslist’.  Another CL win!

Hello World!

November 4th, 2008

This is a test of the blogging software on our site that was recently installed!