Is Access 2003 Conditional Formatting broken in Windows 8?
I have always used conditional formatting to color the background of an active row in a continuous form using Access 2003 and Windows 7. However, I find that in Windows 8 conditional formatting doesn't appear to work other than when the form first opens. Any real time changes don't seem to happen.
Here's the code I am using:
This runs OnCurrent:
Anyone know what is happening here and how I can fix it?
Thanks in advance.
Here's the code I am using:
This runs OnCurrent:
'Set Record Selector: 'Form has an unbound field ctlCurrentRecord
If fTestForControl(frmForm, "ctlCurrentRecord") Then
![ctlCurrentRecord] = frmForm.SelTop
If IsNull(![ID]) Then
Else
![ID].Tag = ![ID].Value 'set ID.Tag
End If
End IfExpression Is: [ID].Tag=[ID]Anyone know what is happening here and how I can fix it?
Thanks in advance.
<<HOWEVER, Windows 8 and Office 2003 are considered to be incompatible...>>
Huh...why is that?
Jim.
Huh...why is that?
Jim.
Jim,
Unless I'm completely misunderstanding it (again, I have not tested it myself):
http://support.microsoft.com/kb/2777626
MS is using pretty strong language here:
"If you have a Microsoft Office 2003 suite or application on your PC, you will have problems running it on Windows 8. We recommend you upgrade Office to a newer version that is compatible with Windows 8."
Unless I'm completely misunderstanding it (again, I have not tested it myself):
http://support.microsoft.com/kb/2777626
MS is using pretty strong language here:
"If you have a Microsoft Office 2003 suite or application on your PC, you will have problems running it on Windows 8. We recommend you upgrade Office to a newer version that is compatible with Windows 8."
<<http://support.microsoft.com/kb/2777626>>
Typical Microsoft strong arm tactics. "This won't work", yet they offer nothing of detail as to why.
And yet Windows 8 includes the desktop specifically so "legacy apps" (non-Metro - oops Metro's out already) can run.
I don't know of anyone using Access 2000/2003 under Windows 2008 either though, so I can't say the article is off base.
Their really trying to push Office 2003 out the door....got an e-mail a few weeks ago stating that starting next year, Office 365 will no longer offer POP3 support and there fore will not support Outlook 2003.
There's no reason for that. Even if they wanted to eliminate POP3 (and they'll have a tough time with that), they could have done what they did in the past, which is write a connector to talk to Office 365 (there was a connector for Office Live).
I love it. Instead of giving people what they want, they give them what they think they should have and then force them into using it no matter what.
I do understand not being able to support old software forever, and there may be something fundamental that does make it incompatible, but this seems long a strong arm tactic to me.
Thanks for the link to the article.
Jim.
Typical Microsoft strong arm tactics. "This won't work", yet they offer nothing of detail as to why.
And yet Windows 8 includes the desktop specifically so "legacy apps" (non-Metro - oops Metro's out already) can run.
I don't know of anyone using Access 2000/2003 under Windows 2008 either though, so I can't say the article is off base.
Their really trying to push Office 2003 out the door....got an e-mail a few weeks ago stating that starting next year, Office 365 will no longer offer POP3 support and there fore will not support Outlook 2003.
There's no reason for that. Even if they wanted to eliminate POP3 (and they'll have a tough time with that), they could have done what they did in the past, which is write a connector to talk to Office 365 (there was a connector for Office Live).
I love it. Instead of giving people what they want, they give them what they think they should have and then force them into using it no matter what.
I do understand not being able to support old software forever, and there may be something fundamental that does make it incompatible, but this seems long a strong arm tactic to me.
Thanks for the link to the article.
Jim.
<<HOWEVER, Windows 8 and Office 2003 are considered to be incompatible...>>
Not surprising, given that Office 2003 extended support ends in April 2014 :)
Not surprising, given that Office 2003 extended support ends in April 2014 :)
ASKER
Guys, we are turning my question into a discussion of Access 2003 / Windows 8 compatibility.
I am most interested at this point in figuring out what is wrong with conditional formatting. Seems odd to me that with most things working just fine in Access 2003, this one thing would be broken.
I personally REFUSE to upgrade from Access 2003. It was the last year they actually got it RIGHT. Ribbons SUCK. Navigation Pane SUCKS. Office 2007 and above is a classic example of MS breaking things that work just fine and ignoring things that are broken.
I am most interested at this point in figuring out what is wrong with conditional formatting. Seems odd to me that with most things working just fine in Access 2003, this one thing would be broken.
I personally REFUSE to upgrade from Access 2003. It was the last year they actually got it RIGHT. Ribbons SUCK. Navigation Pane SUCKS. Office 2007 and above is a classic example of MS breaking things that work just fine and ignoring things that are broken.
<< I am most interested at this point in figuring out what is wrong with conditional formatting>>
Ok - I'll drop out at this point...
You might get other responses, but the real answer very well may be that this and other things are compatibility issues that cannot be fixed.
Ok - I'll drop out at this point...
You might get other responses, but the real answer very well may be that this and other things are compatibility issues that cannot be fixed.
<<Guys, we are turning my question into a discussion of Access 2003 / Windows 8 compatibility.>>
Sorry we got a bit side-tracked, but it is germain to the point. It may not flat out work.
<<I am most interested at this point in figuring out what is wrong with conditional formatting. Seems odd to me that with most things working just fine in Access 2003, this one thing would be broken.>>
Does to me to, but then how Windows works has been fundamentally changed.
I would suggest taking a copy of the DB off the windows 8 machine and try it on another non-windows 8 machine.
If it works, then it's the Office install under Windows 8. If it doesn't work, then it's the DB.
If DB, I would create a new DB and import all objects into it.
If Office, then I'd run a repair and see if that fixes it. If not, then it may be a fundamental incompatibility with windows 8
<<I personally REFUSE to upgrade from Access 2003. It was the last year they actually got it RIGHT. Ribbons SUCK. Navigation Pane SUCKS. Office 2007 and above is a classic example of MS breaking things that work just fine and ignoring things that are broken. >>
I'm on the same page<g>. You could scrape by in Access 2007 and 2010 with an old DB (command bars and ULS were supported as long as you did not covert the DB to the new ACE format), but now with Access 2013, you can no longer do that as command bars have been dropped. So with A2013, it is the ribbon and nothing else.
Jim.
Sorry we got a bit side-tracked, but it is germain to the point. It may not flat out work.
<<I am most interested at this point in figuring out what is wrong with conditional formatting. Seems odd to me that with most things working just fine in Access 2003, this one thing would be broken.>>
Does to me to, but then how Windows works has been fundamentally changed.
I would suggest taking a copy of the DB off the windows 8 machine and try it on another non-windows 8 machine.
If it works, then it's the Office install under Windows 8. If it doesn't work, then it's the DB.
If DB, I would create a new DB and import all objects into it.
If Office, then I'd run a repair and see if that fixes it. If not, then it may be a fundamental incompatibility with windows 8
<<I personally REFUSE to upgrade from Access 2003. It was the last year they actually got it RIGHT. Ribbons SUCK. Navigation Pane SUCKS. Office 2007 and above is a classic example of MS breaking things that work just fine and ignoring things that are broken. >>
I'm on the same page<g>. You could scrape by in Access 2007 and 2010 with an old DB (command bars and ULS were supported as long as you did not covert the DB to the new ACE format), but now with Access 2013, you can no longer do that as command bars have been dropped. So with A2013, it is the ribbon and nothing else.
Jim.
ASKER
Jim,
Yes, it seems that MS made a choice after 2003 to design for 5 year olds with lots of pretty pictures as opposed to true functionality that adults could enjoy.
Have you ever noticed that every time MS "upgrades" their products, everything takes MORE steps and is HARDER to use?
Can you recommend a good simple method for coloring active rows in Windows 8?
* I've also noticed that Windows 8 doesn't care for calculated values in unbound controls but it doesn't mind if you put the calculation in the underlying query and bind it to the field. Weird.
Yes, it seems that MS made a choice after 2003 to design for 5 year olds with lots of pretty pictures as opposed to true functionality that adults could enjoy.
Have you ever noticed that every time MS "upgrades" their products, everything takes MORE steps and is HARDER to use?
Can you recommend a good simple method for coloring active rows in Windows 8?
* I've also noticed that Windows 8 doesn't care for calculated values in unbound controls but it doesn't mind if you put the calculation in the underlying query and bind it to the field. Weird.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Just started working all of a sudden. Thanks everyone.
HOWEVER, Windows 8 and Office 2003 are considered to be incompatible... so while some things may work, you are really stretching your luck if you don't follow the recommendations to upgrade to a newer version of Office.