Front Page not made for large website?

S

Steve Easton

No it's not true. It's a ridiculous myth.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
W

wp

Don't know what you mean by a "large" website.
I run a site with over 700 pages, nearly 100 MB without a hitch.
 
T

Thomas A. Rowe

However, on a large site it is best to break the site into smaller sections (subweb/subsites) to
make managing easier and faster.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
 
T

Tom Pepper Willett

M

Mark Fitzpatrick

Fp works just fine with large sites, though the larger the site, the more
time it takes to communicate with the web server. If you're on a slow
connection then this will be a problem. Also, if the server is real busy a
large site may take longer to publish as the server will take longer to
create a list of files that are on the server.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
 
S

Steve Easton

FP and or visual studio

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
R

Ripper

The myth came about because some servers have a file limit, not a file size
limit, and FP does add a few extra files for each page. My old host told me
the reason I was having so many problems was my website was too large for FP
to handle. I've since moved to another host, added about 50 more pages to
the site and have not had a single crash since the move. It was crashing
almost daily on the other host and every time, they blamed FrontPage. I told
them if they didn't know how to implement FP and disliked it so openly, they
shouldn't offer it as service. They ended up finding the fix to their
problem on another host's discussion forum. It was a glitch in the Apache
files. They still never admitted it wasn't the fault of FrontPage.
 
Top