J
Jackie
I've got the problem that whenever I upload my site (which includes a
database) the write permissions are being overwritten, and I keep having to
wait hours for my host to reset them.
I have other sites containing databases and it's never been a probem before,
however, the latest database is located in the fpdb folder, while the other
isn't.
Searching the archives, I found the following quote from Thomas A. Rowe
suggesting that "the FPDB folder doesn't always maintain write permissions
after publishing updates, which then causes your ASP application to fail to
update the
database."
If that's so, can I get around this problem by just moving the database to
another folder?
Jackie
Sorry, couldn't see how to reply to this from Google groups.
From: Thomas A. Rowe ([email protected])
Subject: Re: Databases - best practices
Newsgroups: microsoft.public.frontpage.client,
microsoft.public.frontpage.extensions.windowsnt
Date: 2000/03/30
FP2K extensions during publishing will sometimes pass along folder
permissions from your local PWS to the remote server.
Examples:
Local sites had browse permission disabled on the root web, and when I
published the site to the remote server, FP also set the root web to be not
allow browsing.
FPDB folder doesn't always maintain write permissions after publishing
updates, which then causes your ASP application to fail to update the
database.
--
=====================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, Email Discussion List,
Newsletter, WebRing, MS KB Quick Links, etc.
database) the write permissions are being overwritten, and I keep having to
wait hours for my host to reset them.
I have other sites containing databases and it's never been a probem before,
however, the latest database is located in the fpdb folder, while the other
isn't.
Searching the archives, I found the following quote from Thomas A. Rowe
suggesting that "the FPDB folder doesn't always maintain write permissions
after publishing updates, which then causes your ASP application to fail to
update the
database."
If that's so, can I get around this problem by just moving the database to
another folder?
Jackie
Sorry, couldn't see how to reply to this from Google groups.
From: Thomas A. Rowe ([email protected])
Subject: Re: Databases - best practices
Newsgroups: microsoft.public.frontpage.client,
microsoft.public.frontpage.extensions.windowsnt
Date: 2000/03/30
FP2K extensions during publishing will sometimes pass along folder
permissions from your local PWS to the remote server.
Examples:
Local sites had browse permission disabled on the root web, and when I
published the site to the remote server, FP also set the root web to be not
allow browsing.
FPDB folder doesn't always maintain write permissions after publishing
updates, which then causes your ASP application to fail to update the
database.
--
=====================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)
FrontPage Resources, Email Discussion List,
Newsletter, WebRing, MS KB Quick Links, etc.