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.
On 9/5/06, Tom Kitta <[EMAIL PROTECTED]> wrote: > I am wondering whatever anyone seen/ has opinion about the following system: > > All information that is presented on a HTML form to end user is build with > information supplied by SQL Server stored procedure. I mean the data that > makes the form + information how form should look like - information > whatever a checkbox should be used or a text field + any special HTML > formatting. > > All that CF does is: parse the result of stored procedure call and build > HTML form based on data provided by stored proc. The CF components can > dynamically build any form based on data from SQL server. CF is used as a > page formatting engine - it formats data provided to it into visually > pleasant form. > > On SQL server there are 1000's of stored procedures which are used to > display form, validate, update, delete etc. Essentialy the form building is > done on SQL server without even looking at any CF code. CF is a black box > which rarely changes while 99% of development is in pure T-SQL (All > developers are SQL experts while most don't know what CF is). > > TK > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:252089 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
