Lebans AlternateColorDetailSection does not work on all pcs mat <mat[ at ]notarealdotcom.adr> 12/17/2008 6:26:54 AM The AlternateColorDetailSection at http://www.lebans.com/alternatecolordetailsection.htm is pretty neat on most pcs. But on a windows 2003 terminal server box it does not seem to render the alternate backcolor, no matter what color I set it to. The color depth is very good via RD on that box, so it's not that the color can't be rendered.

Re: Lebans AlternateColorDetailSection does not work on all pcs mat <mat[ at ]notarealdotcom.adr> 12/19/2008 12:33:32 AM In article <MPG.23b23b883ec0020f989749[ at ]msnews.microsoft.com>, mat[ at ]notarealdotcom.adr says... [Quoted Text] > The AlternateColorDetailSection at > http://www.lebans.com/alternatecolordetailsection.htm > is pretty neat on most pcs. But on a windows 2003 terminal server box it > does not seem to render the alternate backcolor, no matter what color I > set it to. The color depth is very good via RD on that box, so it's not > that the color can't be rendered. > Ping, bonk, bump, help?

Re: Lebans AlternateColorDetailSection does not work on all pcs "Linq Adams via AccessMonster.com" <u28780[ at ]uwe> 12/19/2008 4:03:58 AM When apps run fine on one machine and not on another or run fine in one version and not when run under a newer version, the first thing you have to think about are missing references. Here are Doug Steele's detailed instructions on how to troubleshoot the problem: *** Quote *** Any time functions that previously worked suddenly don't, the first thing to suspect is a references problem. This can be caused by differences in either the location or file version of certain files between the machine where the application was developed, and where it's being run (or the file missing completely from the target machine). Such differences are common when new software is installed. On the machine(s) where it's not working, open any code module (or open the Debug Window, using Ctrl-G, provided you haven't selected the "keep debug window on top" option). Select Tools | References from the menu bar. Examine all of the selected references. If any of the selected references have "MISSING:" in front of them, unselect them, and back out of the dialog. If you really need the reference(s) you just unselected (you can tell by doing a Compile All Modules), go back in and reselect them. If none have "MISSING:", select an additional reference at random, back out of the dialog, then go back in and unselect the reference you just added. If that doesn't solve the problem, try to unselect as many of the selected references as you can (Access may not let you unselect them all), back out of the dialog, then go back in and reselect the references you just unselected. (NOTE: write down what the references are before you delete them, because they'll be in a different order when you go back in) For far more than you could ever want to know about this problem, check out http://www.accessmvp.com/djsteele/AccessReferenceErrors.html Just so you know: the problem will occur even if the library that contains the specific function that's failing doesn't have a problem. **** End Quote **** -- There's ALWAYS more than one way to skin a cat! Answers/posts based on Access 2000/2003 Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-formscoding/200812/1

Re: Lebans AlternateColorDetailSection does not work on all pcs mat <mat[ at ]notarealdotcom.adr> 12/19/2008 6:32:55 AM That's ok generic advice. But the lebans class that handles the alternate colors does not use any special classes and there are no missing references in the app as deployed.

Re: Lebans AlternateColorDetailSection does not work on all pcs mat <mat[ at ]notarealdotcom.adr> 12/19/2008 10:32:39 PM In article <MPG.23b23b883ec0020f989749[ at ]msnews.microsoft.com>, mat[ at ]notarealdotcom.adr says... [Quoted Text] > The AlternateColorDetailSection at > http://www.lebans.com/alternatecolordetailsection.htm > is pretty neat on most pcs. But on a windows 2003 terminal server box it > does not seem to render the alternate backcolor, no matter what color I > set it to. The color depth is very good via RD on that box, so it's not > that the color can't be rendered. > I've done some more testing and it's quite interesting. The class works fine on winxp and vista. It does not work on another windows 2003 box, a box which I'm not accessing via termial services (32 bit color depth!). I can't imagine why the class would fail based on OS?