two people working on same site?

[Guest]

What is the best strategy for two people who are working on the same front
page site from different computers. I want to maintain an updated copy on
my hard drive as does the other person and we do not want to work live, we
want to work on the copy on our hard drive and publish from there. We will
wind up wiping out each others changes if we do that though. The only thing
I can think of is to keep publishing the live site to my hard drive first
before making any changes. Will this publish the changes to the saved copy
on my computer and what is the best way to do this. Any other suggestions.
Thank you

 

[Thomas A. Rowe]

One of you must make changes and then publish to the live/remote site, then the other must open the
live/remote site and publish a copy down to their PC, then make changes and publish back. Repeat as
needed.

--
==============================================
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.
==============================================

 

[Guest]

Thomas, I think I know how but could you go over the steps to publish from
the live site to the pc...and do I publish right to the existing
website...will it overwrite the changes or do I publish to a new file and
then delete the old website? I don't want to screw this up...thank you

 

[clintonG]

FrontPage has a document "check in" and "check out" function that works
fairly well but lacks coordination features. Using IM to message your
peer(s) can work around that lack of coordination in a snap of the mouse
button. As I recall, this may also require working on pages as they reside
on the web server but I never had a problem with that as it just imposed a
little bit of latency in the work flow.

I also used FTP to download resources on a regular basis (regular as in
daily) so I always had local copies that wer up to date. Any losses that
occured due to server failure for example would then have been minimal. Due
to the Server Extension crippleware using FTP with FrontPage is a learning
experience. Download is safe. Uploading when using a local web can result in
problems depending how you are using FrontPage.

This is my "best strategy" that has worked for me and that's why when using
amatuer software such as FrontPage you can't have it both ways and have to
work on the server.

Oh, the other problem when using this method requires a Windows user account
on the web server for each person collaborating with one another. Many
hosting providers refuse to support this requirement.

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/

 

[Guest]

I solved this problem when I was working on my site at work and home with
this program https://secure.logmein.com/go.asp?page=home.

 

[Andrew Murray]

The opposite of publishing to the server. Open the web "live" and go to
file > publish and make the location your pc eg c:\my documents\my webs...