Madscientist and Jeffrey wrote (approximately): > I think the safest design decision here is to create a second table > for your redirection information and use a join in the query to > retrieve it.
I think this is overly cautious. A join uses more server resources and will still require changes to the stored procedure syntax if IMail column names or architecture should change. The chances of IMail changing the basic DDL concept and somehow breaking for good your extra columns are very small, and the workload of changing the name of a column and updating your stored procedure is minimal. Deliberately tag your column name with something site-specific (column names can be quite long) and the chance of IMail requiring a column with the same name is even slimmer. To take advantage of the simplicity of a single table, I'd say go ahead. Many do when integrating with third-party apps. -Sandy Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/
