Hi all:
I've been managing my website with FP2000 for 3 years, and it works great for me. My site is pretty basic HTML with very few effects, but it's a big site with about 60k overall visits per day. I tried a beta version of F2003 a while back, and the first time I published my site using it, it messed up many of my tables and pages and settings, and it took me days to clean everything up. I recently bought a new computer and FP2003, and I want to use FP2003, but I'm scared to death that it will mess me up again the first time I publish. I haven't found any information anywhere about converting from 2000 to 2003.

I copied my entire site over to the new computer, opened it in FP2003 and it looked ok. I clicked the publish button, and told it to compare local to remote sites. It looks like it wants to re-publish every single page on the site, which I really don't want to do. Not sure why it wants to re-publish the entire site. I'm afraid to do this because I don't want it to mess things up. Has anyone converted from FP2000 to 2003 and had any problems? Or am I worried about nothing?
Thanks...

I, too, had a new computer, and installed FP 2003. Win XP Pro. Installed
the IIS 5.1 and FP Server Extensions.

I then did http:// full publish from my old FP 2000 machine to the FP 2003
machine. (you must do this to get in synch. Don't use "changed pages only)

Everything published fine.

Then, each time I had to publish one of my webs to the server, I also did a
full http:// publish the first time to get everything in synch. After that,
changed pages only.

Absolutely no problems.
--
-----
Tom Pepper Willett
Microsoft MVP - FrontPage
http://www.microsoft.com/office/fron...o/default.mspx
http://msdn.microsoft.com/office/und...ing/frontpage/
----
"Zig28" <(E-Mail Removed)> wrote in message
news:8325225B-4537-4322-81D2-(E-Mail Removed)...
| Hi all:
| I've been managing my website with FP2000 for 3 years, and it works great
for me. My site is pretty basic HTML with very few effects, but it's a big
site with about 60k overall visits per day. I tried a beta version of F2003
a while back, and the first time I published my site using it, it messed up
many of my tables and pages and settings, and it took me days to clean
everything up. I recently bought a new computer and FP2003, and I want to
use FP2003, but I'm scared to death that it will mess me up again the first
time I publish. I haven't found any information anywhere about converting
from 2000 to 2003.
|
| I copied my entire site over to the new computer, opened it in FP2003 and
it looked ok. I clicked the publish button, and told it to compare local to
remote sites. It looks like it wants to re-publish every single page on the
site, which I really don't want to do. Not sure why it wants to re-publish
the entire site. I'm afraid to do this because I don't want it to mess
things up. Has anyone converted from FP2000 to 2003 and had any problems?
Or am I worried about nothing?
| Thanks...

PS
To prevent FP2003 from using the new tables layout tools, before you open your Sites in FP 2003, Unselect the Enable Layout Tools
for existing tables option in Tools Page Options General

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
_____________________________________________


"Tom Pepper Willett" <(E-Mail Removed)> wrote in message news:%23$(E-Mail Removed)...
| I, too, had a new computer, and installed FP 2003. Win XP Pro. Installed
| the IIS 5.1 and FP Server Extensions.
|
| I then did http:// full publish from my old FP 2000 machine to the FP 2003
| machine. (you must do this to get in synch. Don't use "changed pages only)
|
| Everything published fine.
|
| Then, each time I had to publish one of my webs to the server, I also did a
| full http:// publish the first time to get everything in synch. After that,
| changed pages only.
|
| Absolutely no problems.
| --
| -----
| Tom Pepper Willett
| Microsoft MVP - FrontPage
| http://www.microsoft.com/office/fron...o/default.mspx
| http://msdn.microsoft.com/office/und...ing/frontpage/
| ----
| "Zig28" <(E-Mail Removed)> wrote in message
| news:8325225B-4537-4322-81D2-(E-Mail Removed)...
| | Hi all:
| | I've been managing my website with FP2000 for 3 years, and it works great
| for me. My site is pretty basic HTML with very few effects, but it's a big
| site with about 60k overall visits per day. I tried a beta version of F2003
| a while back, and the first time I published my site using it, it messed up
| many of my tables and pages and settings, and it took me days to clean
| everything up. I recently bought a new computer and FP2003, and I want to
| use FP2003, but I'm scared to death that it will mess me up again the first
| time I publish. I haven't found any information anywhere about converting
| from 2000 to 2003.
| |
| | I copied my entire site over to the new computer, opened it in FP2003 and
| it looked ok. I clicked the publish button, and told it to compare local to
| remote sites. It looks like it wants to re-publish every single page on the
| site, which I really don't want to do. Not sure why it wants to re-publish
| the entire site. I'm afraid to do this because I don't want it to mess
| things up. Has anyone converted from FP2000 to 2003 and had any problems?
| Or am I worried about nothing?
| | Thanks...
|
|

Thanks Stefan, I checked, and that box is unchecked.

Thanks Tom -- this gives me some confidence... I als had this thought: What if I first use FP2003 to transfer all my remote files on the website down to my local computer by clicking the "remote to local" button when publishing, and overwrite all my local website files. I know the remote site has all of the correct versions of the files. Would that synchronize all the files without having to re-publish the entire site? I'm thinking that if I did that, FP would then have an exact copy of the files on the remote server and the next time I published, it would only publish the changed files rather than the whole site
Thanks...

Doesn't matter which way you publish
(except of course publishing from the latest correct content site)
- you need to Publish All the first time you publish after any version upgrade in FP

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
_____________________________________________


"Zig28" <(E-Mail Removed)> wrote in message news:6D5F1AF8-6AA7-49C5-9908-(E-Mail Removed)...
| Thanks Tom -- this gives me some confidence... I als had this thought: What if I first use FP2003 to transfer all my remote files
on the website down to my local computer by clicking the "remote to local" button when publishing, and overwrite all my local
website files. I know the remote site has all of the correct versions of the files. Would that synchronize all the files without
having to re-publish the entire site? I'm thinking that if I did that, FP would then have an exact copy of the files on the remote
server and the next time I published, it would only publish the changed files rather than the whole site.
| Thanks...