I say definetly switch to dnn. I also had an asp website (directory - www.wisweddingplanner.com) which I wrote code for and had stored the data into an access database. I switched to dnn, and am very glad. No more custom coding, and there is soo much more I have been able to offer visitors on my website. I found a directory module in dnn, great photo gallery, article, contact module and more. This saved me a lot of time, and the modules are very cheap. Oh, and dnn has a great stat tracking system and modules to purchase! I customized my skin to make it more suitable, and is pretty easy to do if you know a little html and css. I am very glad I made the switch, it took a little time to convert and find modules to replace what I had in regular asp but it was worth it. I also found a host who has an automated installation process, and are very helpful. You can check out the websites I have done in dnn: www.encap.net www.feeco.com www.4dimpressions.com www.wisweddingplanner.com www.elitehumancapital.net www.gospotless.com . Good luck, if you have any questions just ask.

______________________

Stephanie

www.FEECO.com | www.ENCAP.net

I'm one of the biggest cynics around here, but in your case for once even I will say yes. This is based on the experience you say you have and also that it sounds like you are talking about providing functionality to other people, presumably as a service.

I gave up on my own little cms system precisely because I'm honest enough to admit I can't possibly hope to compete with a product made by a large group of dedicated developers and also that my goals are primarily in implementing and using the technology, not creating it in the first place.

Rob