It is more of a content management tool.  I have created sites which my clients then alter as well as create new content.  Each website is part of the larger portal.  Access to the website can be done without being able to see any of the other sites on the portal.

DNN is a modular portal.  You will need a module to deal with the database of products.  There are several DNN stores so that your client can add products easily.  They won't have to go into the database at all.

Thanks for your replies - I know I'm asking some really basic questions here, so I appreciate your time.

I have gone through the video and I am very impressed.

It leaves me with some further questions, however:

1. Can you lock down parts of a page so that a particular user can only update a certain block of text, for example, and not edit other parts of the page (the examples in the video show the user editing the entire page). Equally can you set certain pages to be not editable altogether?

2. Can you have an approval system such that a manager can approve all updates before they go live?

3. If I am planning to produce an ASP .net web site with mySQL behind it, will DNN be able to integrate with that set up? (e.g. allow user to upload new products to the database, or delete records, etc)

4. If I cannot integrate the database updating via DNN, can I still use DNN for the rest of the site and design my own pages that are not user editable to upload to the database?

5. How easy is it to migrate sites FROM DNN and TO DNN ?

Thanks,

Flash