Mark, I had those same questions when I first thought about CFCs and such. Along the way, I built a tool called CFSQLTool.

When I started work on CFSQLTool, I spent a lot of time considering how to do table wrappers, create, read, update, delete in a CFC. Soon I realized, the table wrapper should include functions for actor interface as well. So I added functions for list, actor in and actor out. Forms are generated as actor out functions.

The CFSQLTool approach is to build a wrapper that encapsulates all the functions for a table or a view into a CFC.

Not all form data loads to a database. But all forms are data structures. As such, a programmer still has to manage the form's namespaces. A database table is also a structure. The table has well defined namespaces. In cases where the form's data is not targeted for a database, you can still use the database's table design tools to build the form's data structure. Once you have the structure, code generation tools can build the form and get the namespaces to agree. Using this approach, the form is still wrapped in a CFC.

CFSQLTool does require SQL Server and it will work with MSDE. ( Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) is a free, redistributable version of SQL Server 2000 that can now be downloaded from the SQL Server website.)

Joseph




----------------------------------------------------------------------- http://www.switch-box.org/CFSQLTool/Download/

Switch_box                      MediaFirm, Inc.
www.Switch-box.org              Loveland, CO  USA

----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.


CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).

An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]

Reply via email to