@John, Thought that might be the case, just needed to confirm.
@Don, I think it is easy to get mixed up with so many things to learn at times, but take a step back for a minute and have a think about if the project your working on already had a database designed. The code is shunky and in need of a major overhaul, as it is cheaper to redesign than to patch on top of patches to keep the code running. Because the database is already designed, you have to now code to retrieve data, and you write your code as if the data is coming from anywhere, like Dave states it could be coming from a database, webservice or anything. As for conventions for cfwheels, that is the problem they are conventions, conventions can be changed over time or to suit your particular needs, and that means that conventions are not and should not be considered best practice. And being a separate tier to your application, then the way you interface with the database should be your major concern, in other words do I write this level to be modular and interchangeable or do I hard code it in a way that makes slotting new technology in even harder? -- Regards, Andrew Scott WebSite: http://www.andyscott.id.au/ Google+: http://plus.google.com/113032480415921517411<http://plus.google.com/108193156965451149543> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:352019 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
