Long overdue upgrade from MS FP2000 to Frontpage2003

Any known "gotchas" to look out for? Nothing found on site search.

[Webwork]

I just did a site search for upgrade issues and came up with nothing. Maybe I'm searching the wrong phrases. Are there any well known issues or bugs to look out for on upgrading from 2000 to 2003?

What about working on a website built in FP2000 in FP2003?

Just looking for bugs. I've read many threads about the improvements, which is why I'm migrating.

Thanks for any help.

OBTW - Kudos to pageoneresults. Having spent time discussing MSFP with him at the recent PubCon LV I have to say WOW. I mean that. WOW. So very kind of you to take the time to share your depth of knowledge.

[bill]

You're skipping a generation there. ;)
I'm sure you'll be quite happy with the upgrade. You're losing a lot quirks that made FP a number of enemies in the past. FP2K is just too dated compared to FP2003.

In terms of compatibility issues I can't say that I've witnessed many that stick out as being major. I'm able to open backup archive webs of projects I made with FP2K and I don't seem to have any problems with basic functionality. I think you would have more problems working with webs created in FP2003 and trying to open them in FP2K. Backward compatibility shouldn't be a major issue.

[Webwork]

Thanks for the reply Bill. Just looking to avoid adding to my list of things I need to fix. :)

[chopin2256]

The only issue you might have is if you built your site using shared borders in FP2000. I vaguely remember having some problems with the shared borders when I switched versions (it was awhile ago), but definitly do the switch. You can easily redo your shared borders, or use an include.

[Corey Bryant]

You should enjoy the difference. I have not use FP 2000 in a very long time but I was excited aboout 2002 and even more so about 2003.

I love the split view of 2003 (for the coding and the publishing).

-Corey

[M_B_Walker]

I also upgraded, about six months ago. It's a significant improvement, especially the ability to much more easily move from code to design views. I also like how it handles opening multiple web pages at the same time.

The only significant issue I had was converting Shared Borders to Dynamic Web Templates. Not difficult, just a bit awkward and required some cleaning up. But it was well worth the trouble, the DWT is much more flexible (allows multiple templates per site, something that Shared Borders didn't do well).

All in all, I'd make the change again.