Our users currently work on FrontPage webs on local drives, publishing to the server when appropriate. To avoid them having to backup the webs, we'd like to change the default content directory to a network drive.
I followed MS knowledge base article Q194/0/98.ASP FP98: How to Move FrontPage PWS Content to Another Drive, and successfully managed to change from drive C to drive D (also local). However, I seem to hit problems when I try to change to a network drive, but I think this might be because I'm putting in the wrong relative path.
Someone else has suggested that the same outcome can be achieved by publishing the web to the network drive, and then opening it from there. I've tried this, and it seems to be working i.e. it's saving files to the network drive, but I'm just a bit concerned that there's some important reason for not doing it this way which I'll find out at a critical point down the line.
(One of the things which concerns me is that srm.cnf and httpd.cnf still point to the local drive?)
Any info would be gratefully appreciated.
I followed MS knowledge base article Q194/0/98.ASP FP98: How to Move FrontPage PWS Content to Another Drive, and successfully managed to change from drive C to drive D (also local). However, I seem to hit problems when I try to change to a network drive, but I think this might be because I'm putting in the wrong relative path.
Someone else has suggested that the same outcome can be achieved by publishing the web to the network drive, and then opening it from there. I've tried this, and it seems to be working i.e. it's saving files to the network drive, but I'm just a bit concerned that there's some important reason for not doing it this way which I'll find out at a critical point down the line.
(One of the things which concerns me is that srm.cnf and httpd.cnf still point to the local drive?)
Any info would be gratefully appreciated.