Thanks for your feedback Spooky.>>The first part is the planning.
It may save a lot of hassle in the long run, if you can visualise the design and requirements of the database.>>
Here's an example of what may apply in my situation:
http://www.chatswoodshopping.com.au
>>I would consider the database first and use it as a resource for generating active template pages.>>
Do you mean create the access db first, followed by the front end design of the pages involved?
>>Most of your site can continue to be html, and only the results listing page and the individual item page may need to be asp.>>
Could you explain this further, so I can understand what you mean.
>>A search returns a list. A list links to an item.>>
Explain more please..
Will you have a table of suppliers?
will you have a table of categories? Will it be a flat file? etc
Explain more...
Keep your explanations simple as possible - never created db sites as yet
Thank you
Herman