[AccessD] Observations on AC 2007 (not good)...more

Here's more on 2007....
I was reviewing a copy of the Tradewinds application rewritten for 2007.
There was a subform set to datasheet view that only displayed a few selected
columns...
It was the subform in the Employee Detail form that showed the related
orders to the salesperson.
I could not find a property to "hide" the fields on the subform.
After some research, I ran some VBA code in the Activate event handler, and
was able to determine that there was an unexposed property called
ColumnHidden. Sure enough, it was set to "True" for the columns not showing
up.
However, it remains a mystery how they ever got set that way in the first
place....there was no VBA proc in the modules to do this. It appears as
though "someone" coded it, and then erased it.

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Jim Lawrence
> Sent: Thursday, November 25, 2010 1:40 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Observations on AC 2007 (not good)
>
> Hi Mark:
>
> I started converting a project from AC 2003 to AC 2007 but
> ran into so many issues that I told the client that 2007 was
> not worth and it would be a good savings in the long run to
> jump right into 2010. Never having used 2010 it was a bit of
> a jump of faith but I thought how much worse could it be. It
> was a good choice.
>
> I believe the 2007 should be avoided at all costs, just like
> the OS (a name that must not be spoken) and move straight to
> Win7 or in our case Access 2010.
>
> Thanks for the your warnings and investigations. Do not
> hestitate to post any of your other finds.
>
> Jim