how do you remove a fp2003 website so you can change to a fp2000 w

[Dennis]

I published a web site using fp2003. I have fp2000 on my laptop with which
I'm more familar with and it has image composer. i would like to delete the
fp2003 website and replace it with one I would create in fp2000. Why? im
just more use to fp2000 and don't know my way around fp2003 yet. also when I
publish in 2003 its not backword compatible with 2000 so I can't modify the
web pages with fp2000 on my laptop. It won't let me publish, gets port 80
error So I would like to completely remove the site and create a new one buy
I can't get rid of the one thats on there now

 

[Thomas A. Rowe]

FP2000 can open and work on a site created in FP2003 (I do this daily). You have other issues if you
can not open or access the site after using FP2003.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

 

[Andrew Murray]

You can open *any* FP web in any version. So you can use FP2003 to open
your old site, or FP2000 to open your current site....

So just use FP 2000 to work on your site.

The compatibility issue shouldn't have anything to do with one version
working the other not.

I'm sure in normal circumstances, you should be able to open a web done in
FP 2003 with FP 2000 live on the server, as long as it has at least the 2000
FP server extensions. (FP2003 uses the 2002 SE so that shouldn't be a drama,
only the features introduced after FP2000 will not work with 2000 SE even if
you use a later FP release

Can you connect to the live server in FP2000 and just delete the files of
the web done in FP 2003?

or, connect to the live server with FP2003 and delete the files.

Then in FP2000, make sure your connection/publish settings are all correct;
if you still have problems check with your host.

 

[Tina Clarke]

FP2000 can open and work on a site created in FP2003 (I do this daily). You have other issues if you
can not open or access the site after using FP2003.

Plus you can put IC on your laptop .. you don't have to have fp2000 as well
though you can have if you want I've got all of the fp versions except fp97
on my computer... but I use fp03 to work in.

hth Tina

--
http://accessfp.net/ - FrontPage Tutorials
http://anyfrontpage.com/ - http://frontpage-ebooks.com/
http://addonfp.com/ - FrontPage Addons
http://frontpage-tips.com/ - Weekly FrontPage Tips
http://msmvps.com/frontpage/ - FrontPage News & Articles Blog
http://frontpage-advice.blogspot.com/ - FrontPage Advice Blog
http://artdoodle.com/ - Abstract Pen and Ink Drawings

 

[Dennis]

I can open it but it won't take my username and password. comes badk with
username and pasword blank

 

[Dennis]

I can open it but it won't take my username and password. comes badk with
username and password blank. so I can open it work on it but when it comes to
publish it asks for user name and password and thats as far as I get

 

[Dennis]

I can open it but it won't take my username and password. comes badk with
username and password blank. so I can open it work on it but when it comes to
publish it asks for user name and password and thats as far as I get

 

[Dennis]

I think I might have figured it out. when I installed fp2000 on my laptop I
didn't install the extensions, as done in custom install

 

[Andrew Murray]

The Server Extensions reside on the web server, not on your machine and you
don't usually install them, your host would do this (or else they have a
web-based toolbox thing that can do this for you).

You can have IIS installed on your computer along with the FPSE but this is
intended more as a test environment(to check the behaviour of those
components that use the FPSE), not for serious web hosting unless you have
all the security measures and so on in place, and you intend to physically
host your own site.