Expanded Content? Database or html?

> The problem is that this content needs formatting and I've heard that it's
> not the best practice to put html into a database.

The idea is to separate presentation from data as best as you (practically)
can.

If all 4,500 will be styled the same, then this is easy. If each of the
4,500 need separate style formatting, then, yea, you'll just want to store
the HTML in with the data itself as a TEXT field.

You definitely would be better off with one HTML page calling one of 4,500
records rather than 4,500 individual static web pages.

-Darrel

You don't necessarily put the who HTML page into the database, you only put
the necessary HTML tags in with it.

So maybe you have something like this:
tblProduct
-------
title
picture
description

"title" would get outputted maybe into an <h1> block on your 'master' page.
The "picture" a link that is put into an <img> tag.
"description" would be the main text with some tags, as needed... maybe
like:
<p>The <strong>XYZ Widgets</strong> are made from durable cat hair.</p>

See??

"Lee" <lee_nospam_@artjunky.com> wrote in message
news:f78jlk$slj$1@forums.macromedia.com...
>I have a list of products that need content.
>
> Basically this extended information needs to display details that can't be
> listed with regular product details, it's just too much.
>
> My dilemma is that I can't decide whether to post it to the web in
> individual html files or to post it to a database where that content is
> pulled out. I visited a larger company recently that has roughly 70,000
> products and 3 web people to create individual pages for expanded product
> information. I only have 4500 products and it's just me doing the work.
>
> Are these really the only two options or are there others? XML?
>
> The problem is that this content needs formatting and I've heard that it's
> not the best practice to put html into a database.
>
> I'm just curious what others are doing.