This reminds me of a project, several years ago, where we webified some SAP information. The VB programmer "needed" to put the HTML in the ..DLLs and it was a total pain in the ass to make any changes. They also insisted that ASP pages were the only method of consuming the COM objects. This is how the project was "sold" to IT mgt at the time.
I suggested that they create a much-simpler COM object that returned only data and then CF would then consume the object and create the HTML. I even created simple COM objects to prove this to them. However, I lost out to the Indian consultants and eventually lost my job. Boo-hoo. Now, that I have had time to look back over this issue, I still fully-realize how immensely stupid it was for them to mix the model and presentation in their COM .DLLs. However, for the consultants, it was pure genius since very few people knew how to make the changes. When I take looks at that company's web site(s), I see how very little they have progressed with that sort of mentality. M!ke -----Original Message----- From: John Blayter [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 05, 2006 3:07 PM To: CF-Talk Subject: Re: ColdFusion as presentation engine and nothing more IMHO... Use the systems for what they are designed for. Sure SQL server can generate HTML but is that the best way to maintain it? The thought of having to sort through thousands of stored procs instead of some kind of file system to make a presentation change just sounds like my personal version of hell. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:252116 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
