Access the answers to your technology questions today.
Subscribe Now
30-day free trial. Register in 60 seconds.
What Makes Experts Exchange Unique?
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
Subscribe Now
30-day free trial. Register in 60 seconds.
Join the Community
Give a Little. Get a Lot.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Join the Community
by: guadalupePosted on 2003-04-24 at 11:53:24ID: 8390504
For got one detail, yes I could just put:
<!-- #include file="thisPagesCode.asp" -->
But given I will be out putting record sets into tables and forms it begins to mixup content with code as some html fragments will be with the code and I would like to avoid this as it defeats the idea of keeping all design centrelized in XSL. I also have a method for converting ADO RecordSets to xml and could merge the XML record sets with the "content xml" and then use the larger XMLDOM doc to generate the final content but I lose the ability to generate the "static" versions of the asp using the much less dynamic content maintained by the back office content editor. Instead the xml/xsl merging would happen for EVERY request. Less than optimum. Thanks