>>What if in 6 months time the client comes back and says I need extra functionality.
If the clients has new requirements, then I'll submit an estimate for the extra costs. The idea is not having him to pay for something he doesn't need, only for extras when he need extras. Cross tables are more complex to handle, so why make it simple when you can make it complicated huh ? In the example I gave, I started with about 8 areas users could be allowed, now I have about 20 in the project, and the same code using a list in one field is still working like a charm. If the client now claims he need 200 activities, the cost to convert the present system to use a cross table instead of a list will just be marginal, compared to the cost of developing the 180 new activities! ;-) I also have plenty of items using cross tables, when it is better to use a cross table. My point is just that it is NOT true that cross tables are always better, ... execept in books ;-) -- _______________________________________ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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/SQL/message.cfm/messageid:2565 Subscription: http://www.houseoffusion.com/groups/SQL/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.6
