administrative changes

[jhb]

I have been asked to create a site that allows the client to administrate some of the content. They mentioned “administrative pages.”

How do I make these “administrative pages”? How do the changes they make get to the web? Do they FTP these pages themselves? What if the pages they are changing are dynamic? Are these the same pages I made for he original design that I send them? How do I give them access to the pages?

Can you direct me to a site, tutorial, or anything that would answer these questions?



Thank you,



Justin

[Vladdy]

The best way of approaching the problem would depend on the type of content they need to change, such as news pages, profile pages, etc.
In general administrative page would have a form that allows to add content that is stored in a DB or file and retrieved by a server side script when processing page request.
For example this (or any other) forum. Just think about "New Reply" page as administration page that allows you to add content to the website.

[jhb]

I believe I will be using an Access backend with ASP scripting. Where can I find some code that will help me to understand exactly what is needed for the user to access the content n the DB? Thanks for your help.

[snallan]

There are tons of tutorials available for asp. Some of them I found useful are
www.4guysfromrolla.com
www.w3schools.com
www.asp101.com

[jpmoriarty]

if your site is in any way popular then i'd strongly suggest staying away from access. im not sure how to connect to it with ASP, but i'd strongly recommend mysql (www.mysql.com), but i presume that if you're using a web hoster then then will have something that's better than access (MS SQL server or MySQL)

[jhb]

I think this project is calling for Access Db t o be used. I'm really looking for code snippets or tutorials on how to allow the client to get into the DB, make changes to the content, and then update that page themselves. If you have any suggestions on where I can find this info. please let me know. Thanks.

[jpmoriarty]

sorry to be straying off topic, but mind if i ask why "I think this project is calling for Access Db to be used"?

Access is not good at having concurrent users, particularly if you have more than 5 or so. Hence it makes it appalling at being a web site DB, since all you need is three or four visitors and you can have the whole thing crashing down.

MySQL and MS SQL are database servers (as opposed to an application) and hence love lots of people looking at their data, all at the same time.

If you go to http://www.mysql.com/information/benchmarks.html then the second test compares the speed of MySQL compared to access, and that's before you even consider the failings of access with regard to multiple requests.