Hmm. According to CC it should be working. I can't imaging what I might be doing wrong, the process seems simple enough to be a no-brainer, but I'm going to have to re-visit it and see what I can find out when I get some time to geek out with web stuff again.

Spinny,

Please see my post under the thread entitled "VSD-Trouble trying to change visited and unvisited link colors." I just tested the procedure I detailed in my post by closing my web site, exiting VSD, starting VSD, and re-opening my web site, and my custom defined colors are still intact. (They don't appear under the Custom colors section, though, because VSD begins with no custom defined colors when first started.) I've also viewed them in IE, so the page link colors can be changed if every step of the procedure I've described is followed.

Tom

Tom,

Very much appreciate the input, as well as the validation that this really is a problem. I'll follow your guide this evening and see how it goes; I'll post my results.

Thanks!

Tom,

You may want to edit your instruction post and put it in the tricks and tips section for VSD.

I just got a response from tech support:



I'll cross-post this to both threads for completeness.

Spinny & BillR,

I just did some additional testing and discovered that once the default Page link colors have been changed on the Home page using two Basic colors, they can be changed on all pages using any colors (Basic or Custom). The key appears to be completing the change on the Home page first by clicking on the OK button after two Basic colors have been selected for the visited and unvisited links color boxes. After this has been done, custom colors can be selected and applied to all pages without first applying them to the Home page by itself. So, the last three steps of the procedure I described in the other thread can be reduced to one step. I will modify them and post the entire procedure in the Tricks and Tips section per BillR's recommendation. I'll also post this message in both threads.

Tom

Thanks, Tom. For what it's worth I just tried the work-around from tech support that I posted above and that worked, too.