but why store tags in a DB?<BR><BR>current thinking is to keep content in the DB, and leave the formating (tags) in the ASP page....<BR><BR>anything is possible...<BR><BR>where there's a will (and a db)...there's a way.
So this means in affect that converting for instance the website i have in mind which is stored in folders on a webserver into a database driven website i would have to remove all the tags and reformat the documents.I am looking at about 4000 pages.
Any admin tools you ever end up building to automate the update of these 4000 pages would have to include functionality to store content WITH tags. That's a nightmare.<BR><BR>Depending on how your pages are formated- you could potentially have one ASP page that has all the formating, and then you could dynamically populate this page with the database content.<BR><BR>If ever you decided to redesign your site, you have to redesign ONE page, not 4000.<BR><BR>You could store path information to those 4000 pages in the database as an alternative....<BR><BR>What I wanna know is- who's idea was it to have 4000 static web pages without even considering a database alternative?
My boss is having me do a site like this.. Its for search engine rankings. Dont ask me I agree with you. But anyways the way I did it was have a template that has the formatting and then an asp script creates the pages as needed. If we ever need to redesign the layout we do it on the one file and the regenerate all the pages with a script. If theres a will theres a way :)