>>I used pipes because sometimes, the client-entered options for these data bits contain commas.
If your app lets the client enter his own options, you may be better with a separate table. Using a list in one field in one table is much easier to handle programmatically only under two conditions: 1. you have no more than a couple of 10 options; 2. you can keep a control of the number and type of possible options; In my case, I only have 2 characters options each one represents an item a user can work on in the intranet, ie: if a user has a string like "DO,NR,AG,PA" he is allowed to work on Documents, News Releases, Agenda and Pages in the Web site. Users cannot define new options, only the programmer when a new activity must be added to the system. -- _______________________________________ 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:2554 Subscription: http://www.houseoffusion.com/groups/SQL/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.6
