I think Aaron makes a good point. I have always had to wear all the hats - project manager, information architect, business analyst, graphic artist etc - database developer and coder. I think that is more often than not the case. So if I'm building the db and doing the coding the logical and physical are the same to me. Or, to state another way, I don't see an employee object, I see an employee object related to an address object, also related to a department object etc.
I may or may not build a component that gloms all of those into one Employee object. I usually do not. But I can see the advantage of Robert's approach. Robert have you considered moving from SPs to LINQ and feeding ColdFusion .net objects (assuming you're on CF8)? I don't know how well it would work, or even if it is possible since I haven't done it - just curious to find out if it can be done and what your thoughts were. Cheers, Shane --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. To unsubscribe, send email to [email protected] For more options, visit http://groups.google.com/group/houcfug?hl=en -~----------~----~----~----~------~----~------~--~---
