I wouldn't count on them being deleted from the files folder, VSD is hit-or-miss with cleaning out stuff from there. Best bet is to manually delete everything in there and then re-save; it'll re-populate the folder based on what's currently being used.

I think the best way to save the old buttons is to make a temp page, then copy/paste them into that page for safe keeping (it'll retain their current position if you make the temp page the same size as the original one). Then you can delete them from your working page with confidence. Don't just make a clone of the whole page, there's a bug in VSD that screws up the button code on the new ones when you do that. Clone the page, then delete the cloned buttons and manually copy/paste the originals into the new temp page.

Oh, and to echo Cary: no need to feel like an idiot. I'd be using that attribute the same way, most likely, if I hadn't already read about how it's supposed to work. No way of knowing otherwise unless someone tells you.

Thanks for all your suggestions, but it's not going to be easy for me to implement them because I've used this same scheme on about 25 pages in my web site. I was just wondering, does VSD 6 use the Title attribute?

I asked for it, but Tom said it was too late to implement in time for 6.0, unfortunately.

That's a bummer! I guess I'll just have more work for a web site developer friend of mine to do before I launch this thing and get it out of my hair.

Are you going to need to do any serious maintenance in VSD once you launch it? It'd not be hard to insert the title attributes manually, just search for every place with an alt and add title right after it. Even 25 pages aren't so bad when you're just pasting in the text. It'd work unless you planned to upload future updates via VSD.

There shouldn't be too many things to fix when I'm done with it and ready to launch. All of my pages contain pretty basic stuff (at least I think they do), so there shouldn't be very much that needs to be fixed. The main thing I'm going to have my friend do is fix the code so that these Print, Save, and Email commands work like they're supposed to. Currently they don't because VSD doesn't provide the print.css capability (without inserting an HTML object), which is a bit over my head and too time consuming for me because of all the other stuff I'm working on.

As far as future updates goes, I haven't decided what I'm gonna do about them. I know I'll probably have to leave VSD behind at some point, but I'm not sure exactly when that will be. Plus, I'm not sure what I'll use to take its place. I hope to hand this job off to someone who does this kind of thing for a living because there's gonna be ongoing maintence and updates that will have to be done. But I'll cross that bridge when I get there. Right now all I want to do is finish a book I'm working on that will supplement the web site. Until the book is done, I won't launch because the two go hand in hand.

Well, some of the gurus around here can whip out an entire web site with a copy of Wordpad and a can of Red Bull. Failing that virtuoso level, I hear good things about CC's HTML Editor. I have a copy and just haven't yet taken time to get to know it. I think I've learned enough HTML to be dangerous now.

HTML dangerous? Or could it be that you are now dangerous with the knowledge of HTML that you now hold in your arsenal?

I keep a "test" page on my desktop of my Eee sub-laptop. While watching tv at night with the wife, I keep adding HTML code to it, just to experiment with it and hopefully learn something. She's getting agrevated at me cause I have now discovered several FLASHY and Annoying tags, along with the noisy ones. I guess it's time to tone it down for a while

Heh. Dangerous to any poor, innocent web site I get my grubby paws on.