RE: SQL Server 7.0 Stored Procedures
Excelent!...thanks Jay. When I first started to use CF I always wondered why it didn't ask for the size of the varchar param Personally I think it would be usefull for this to be compulsory as it is at the other end in SQL. -- Andrew Ewings Project Manager Thoughtbubble Ltd http://www.thoughtbubble.net -- United Kingdom http://www.thoughtbubble.co.uk/ Tel: +44 (0) 20 7387 8890 -- New Zealand http://www.thoughtbubble.co.nz/ Tel: +64 (0) 9 419 4235 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0)207 387 8890. -Original Message- From: Jay White [mailto:[EMAIL PROTECTED]] Sent: 02 November 2000 14:57 To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures OK, I figure out my problem with truncated output parameters in stored procedures. When you create the parameter with CF, there is an 'optional' MAXLENGTH parameter that you can set. If you do not specify the MAXLENGTH for varchar, it defaults to 255. That explains the truncation of the varchar(2000) output parameter that I was trying to get from the stored proc. It is probably good practice to always use the MAXLENGTH, even though it is optional, because even a VARCHAR(1) would be set up as a VARCHAR(255) . . . Thanks anyway, Jay White Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED] Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED]
RE: SQL Server 7.0 Stored Procedures
OK, I figure out my problem with truncated output parameters in stored procedures. When you create the parameter with CF, there is an 'optional' MAXLENGTH parameter that you can set. If you do not specify the MAXLENGTH for varchar, it defaults to 255. That explains the truncation of the varchar(2000) output parameter that I was trying to get from the stored proc. It is probably good practice to always use the MAXLENGTH, even though it is optional, because even a VARCHAR(1) would be set up as a VARCHAR(255) . . . Thanks anyway, Jay White Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED]
RE: SQL Server 7.0 Stored Procedures
Check the adm panel in your cf and tick the option datasources->yourdatasource(click on name)-> cfsettings->enable retrieval of long text. good luck. -Original Message- From: Jay White [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 3:00 PM To: CF-Talk Subject: SQL Server 7.0 Stored Procedures Hello I am having touble with output parameters when running SQL Server 7.0 stored procedures. All varchar output parameters get truncated to 255(when using ODBC) or 256(when using OLEDB) characters. I can run the same stored procedure from ASP (with either ODBC or OLE) without truncation. I have tried both CF 4.0 and 4.5 with updated service packs. CF is running on a NT 4.0 Server with most recent service pack and updated MDAC. I find it hard to believe that this is a limitation to ColdFusion, so I am guessing that I do not have something set up correctly. Please email directly if anyone has any ideas. Thanks, Jay White Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED] Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED]
RE: SQL Server 7.0 Stored Procedures
OK. I was unaware that the default number of characters returned by Query Analyzer can be changed... good to know. I don't think it can be done in "return". he important concept here is that what a tool shows you, is not always ALL the data. ~Simon -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 10:42 AM To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures Simon If you are using Query analyser you can change the maximum number of characters that are returned. If you go to query - current connection options and then select the advanced tab you can change it from 256. There is a maximum (not sure what it is). I'm not sure how you do this using "Return all rows" -- Andrew Ewings Project Manager Thoughtbubble Ltd http://www.thoughtbubble.net -- United Kingdom http://www.thoughtbubble.co.uk/ Tel: +44 (0) 20 7387 8890 -- New Zealand http://www.thoughtbubble.co.nz/ Tel: +64 (0) 9 419 4235 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0)207 387 8890. -Original Message- From: Simon Horwith [mailto:[EMAIL PROTECTED]] Sent: 01 November 2000 15:14 To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures I'm refering to the SQL Server "return all rows" menu option when right clicking on a table. Visual query builder is one of MS's query building tools...very similar to the CFStudio visual query builder in terms of their interfaces. Actually, I meant to say "Query Analyzer" (an SQL query execution environment in SQL Server), but the "255" rule still holds true for these environments, regarding their respective outputs. ~Simon -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 10:06 AM To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures what do you mean by "show rows" interface and visual query buider? I assume these are interfaces built within CF. When you execute a query through ISQL you get a maximum of 256 characters per coloumn by default returned (I guess this is using OLEDB) but you can change this setting in the query options. I assume CF must be doing something similar as I'm sure SQL will return the full value via ODBC/OLEDB to CF. -- Andrew Ewings Project Manager Thoughtbubble Ltd http://www.thoughtbubble.net -- United Kingdom http://www.thoughtbubble.co.uk/ Tel: +44 (0) 20 7387 8890 -- New Zealand http://www.thoughtbubble.co.nz/ Tel: +64 (0) 9 419 4235 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0)207 387 8890. -Original Message- From: Simon Horwith [mailto:[EMAIL PROTECTED]] Sent: 01 November 2000 15:04 To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures SQL Server (6.5, anyway) does store the first 255 characters in the actual database and other excess characters in a "database extension" file. When querying data, you should still get all characters, though. When viewing data in studio, visual query builder, or the default "show rows" interface, you will only be shown a truncated value, though. my 2 cents. ~Simon -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 9:58 AM To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures Interesting! When I started to develop SP's a few years ago I was told to make the ma
RE: SQL Server 7.0 Stored Procedures
Simon If you are using Query analyser you can change the maximum number of characters that are returned. If you go to query - current connection options and then select the advanced tab you can change it from 256. There is a maximum (not sure what it is). I'm not sure how you do this using "Return all rows" -- Andrew Ewings Project Manager Thoughtbubble Ltd http://www.thoughtbubble.net -- United Kingdom http://www.thoughtbubble.co.uk/ Tel: +44 (0) 20 7387 8890 -- New Zealand http://www.thoughtbubble.co.nz/ Tel: +64 (0) 9 419 4235 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0)207 387 8890. -Original Message- From: Simon Horwith [mailto:[EMAIL PROTECTED]] Sent: 01 November 2000 15:14 To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures I'm refering to the SQL Server "return all rows" menu option when right clicking on a table. Visual query builder is one of MS's query building tools...very similar to the CFStudio visual query builder in terms of their interfaces. Actually, I meant to say "Query Analyzer" (an SQL query execution environment in SQL Server), but the "255" rule still holds true for these environments, regarding their respective outputs. ~Simon -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 10:06 AM To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures what do you mean by "show rows" interface and visual query buider? I assume these are interfaces built within CF. When you execute a query through ISQL you get a maximum of 256 characters per coloumn by default returned (I guess this is using OLEDB) but you can change this setting in the query options. I assume CF must be doing something similar as I'm sure SQL will return the full value via ODBC/OLEDB to CF. -- Andrew Ewings Project Manager Thoughtbubble Ltd http://www.thoughtbubble.net -- United Kingdom http://www.thoughtbubble.co.uk/ Tel: +44 (0) 20 7387 8890 -- New Zealand http://www.thoughtbubble.co.nz/ Tel: +64 (0) 9 419 4235 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0)207 387 8890. -Original Message- From: Simon Horwith [mailto:[EMAIL PROTECTED]] Sent: 01 November 2000 15:04 To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures SQL Server (6.5, anyway) does store the first 255 characters in the actual database and other excess characters in a "database extension" file. When querying data, you should still get all characters, though. When viewing data in studio, visual query builder, or the default "show rows" interface, you will only be shown a truncated value, though. my 2 cents. ~Simon -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 9:58 AM To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures Interesting! When I started to develop SP's a few years ago I was told to make the maximum size of my varchar variables 255 but never new why! The company I worked for didn't use ColdFusion so I assume this is due to the ODBC restriction you are talking of. I am confused though because if you are using a DSN for both CF and ASP then it will be using the same ODBC driver for SQL Server and so you should see the same results. I'm confused as to where the source of the problem is. I'll have a think!... ---
RE: SQL Server 7.0 Stored Procedures
I'm refering to the SQL Server "return all rows" menu option when right clicking on a table. Visual query builder is one of MS's query building tools...very similar to the CFStudio visual query builder in terms of their interfaces. Actually, I meant to say "Query Analyzer" (an SQL query execution environment in SQL Server), but the "255" rule still holds true for these environments, regarding their respective outputs. ~Simon -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 10:06 AM To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures what do you mean by "show rows" interface and visual query buider? I assume these are interfaces built within CF. When you execute a query through ISQL you get a maximum of 256 characters per coloumn by default returned (I guess this is using OLEDB) but you can change this setting in the query options. I assume CF must be doing something similar as I'm sure SQL will return the full value via ODBC/OLEDB to CF. -- Andrew Ewings Project Manager Thoughtbubble Ltd http://www.thoughtbubble.net -- United Kingdom http://www.thoughtbubble.co.uk/ Tel: +44 (0) 20 7387 8890 -- New Zealand http://www.thoughtbubble.co.nz/ Tel: +64 (0) 9 419 4235 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0)207 387 8890. -Original Message- From: Simon Horwith [mailto:[EMAIL PROTECTED]] Sent: 01 November 2000 15:04 To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures SQL Server (6.5, anyway) does store the first 255 characters in the actual database and other excess characters in a "database extension" file. When querying data, you should still get all characters, though. When viewing data in studio, visual query builder, or the default "show rows" interface, you will only be shown a truncated value, though. my 2 cents. ~Simon -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 9:58 AM To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures Interesting! When I started to develop SP's a few years ago I was told to make the maximum size of my varchar variables 255 but never new why! The company I worked for didn't use ColdFusion so I assume this is due to the ODBC restriction you are talking of. I am confused though because if you are using a DSN for both CF and ASP then it will be using the same ODBC driver for SQL Server and so you should see the same results. I'm confused as to where the source of the problem is. I'll have a think!... -- Andrew Ewings Project Manager Thoughtbubble Ltd http://www.thoughtbubble.net -- United Kingdom http://www.thoughtbubble.co.uk/ Tel: +44 (0) 20 7387 8890 -- New Zealand http://www.thoughtbubble.co.nz/ Tel: +64 (0) 9 419 4235 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0)207 387 8890. -Original Message- From: Jay White [mailto:[EMAIL PROTECTED]] Sent: 01 November 2000 15:00 To: CF-Talk Subject: SQL Server 7.0 Stored Procedures Hello I am having touble with output parameters when running SQL Server 7.0 stored procedures. All varchar output parameters get truncated to 255(when using ODBC) or 256(when using OLEDB) characters. I can run the same stored procedure from ASP (with either ODBC or OLE) without truncation. I have tried both CF 4.0 and 4.5 with updated serv
RE: SQL Server 7.0 Stored Procedures
what do you mean by "show rows" interface and visual query buider? I assume these are interfaces built within CF. When you execute a query through ISQL you get a maximum of 256 characters per coloumn by default returned (I guess this is using OLEDB) but you can change this setting in the query options. I assume CF must be doing something similar as I'm sure SQL will return the full value via ODBC/OLEDB to CF. -- Andrew Ewings Project Manager Thoughtbubble Ltd http://www.thoughtbubble.net -- United Kingdom http://www.thoughtbubble.co.uk/ Tel: +44 (0) 20 7387 8890 -- New Zealand http://www.thoughtbubble.co.nz/ Tel: +64 (0) 9 419 4235 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0)207 387 8890. -Original Message- From: Simon Horwith [mailto:[EMAIL PROTECTED]] Sent: 01 November 2000 15:04 To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures SQL Server (6.5, anyway) does store the first 255 characters in the actual database and other excess characters in a "database extension" file. When querying data, you should still get all characters, though. When viewing data in studio, visual query builder, or the default "show rows" interface, you will only be shown a truncated value, though. my 2 cents. ~Simon -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 9:58 AM To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures Interesting! When I started to develop SP's a few years ago I was told to make the maximum size of my varchar variables 255 but never new why! The company I worked for didn't use ColdFusion so I assume this is due to the ODBC restriction you are talking of. I am confused though because if you are using a DSN for both CF and ASP then it will be using the same ODBC driver for SQL Server and so you should see the same results. I'm confused as to where the source of the problem is. I'll have a think!... -- Andrew Ewings Project Manager Thoughtbubble Ltd http://www.thoughtbubble.net -- United Kingdom http://www.thoughtbubble.co.uk/ Tel: +44 (0) 20 7387 8890 -- New Zealand http://www.thoughtbubble.co.nz/ Tel: +64 (0) 9 419 4235 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0)207 387 8890. -Original Message- From: Jay White [mailto:[EMAIL PROTECTED]] Sent: 01 November 2000 15:00 To: CF-Talk Subject: SQL Server 7.0 Stored Procedures Hello I am having touble with output parameters when running SQL Server 7.0 stored procedures. All varchar output parameters get truncated to 255(when using ODBC) or 256(when using OLEDB) characters. I can run the same stored procedure from ASP (with either ODBC or OLE) without truncation. I have tried both CF 4.0 and 4.5 with updated service packs. CF is running on a NT 4.0 Server with most recent service pack and updated MDAC. I find it hard to believe that this is a limitation to ColdFusion, so I am guessing that I do not have something set up correctly. Please email directly if anyone has any ideas. Thanks, Jay White Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED] ---
RE: SQL Server 7.0 Stored Procedures
SQL Server (6.5, anyway) does store the first 255 characters in the actual database and other excess characters in a "database extension" file. When querying data, you should still get all characters, though. When viewing data in studio, visual query builder, or the default "show rows" interface, you will only be shown a truncated value, though. my 2 cents. ~Simon -Original Message- From: Andy Ewings [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 9:58 AM To: CF-Talk Subject: RE: SQL Server 7.0 Stored Procedures Interesting! When I started to develop SP's a few years ago I was told to make the maximum size of my varchar variables 255 but never new why! The company I worked for didn't use ColdFusion so I assume this is due to the ODBC restriction you are talking of. I am confused though because if you are using a DSN for both CF and ASP then it will be using the same ODBC driver for SQL Server and so you should see the same results. I'm confused as to where the source of the problem is. I'll have a think!... -- Andrew Ewings Project Manager Thoughtbubble Ltd http://www.thoughtbubble.net -- United Kingdom http://www.thoughtbubble.co.uk/ Tel: +44 (0) 20 7387 8890 -- New Zealand http://www.thoughtbubble.co.nz/ Tel: +64 (0) 9 419 4235 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0)207 387 8890. -Original Message- From: Jay White [mailto:[EMAIL PROTECTED]] Sent: 01 November 2000 15:00 To: CF-Talk Subject: SQL Server 7.0 Stored Procedures Hello I am having touble with output parameters when running SQL Server 7.0 stored procedures. All varchar output parameters get truncated to 255(when using ODBC) or 256(when using OLEDB) characters. I can run the same stored procedure from ASP (with either ODBC or OLE) without truncation. I have tried both CF 4.0 and 4.5 with updated service packs. CF is running on a NT 4.0 Server with most recent service pack and updated MDAC. I find it hard to believe that this is a limitation to ColdFusion, so I am guessing that I do not have something set up correctly. Please email directly if anyone has any ideas. Thanks, Jay White Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED] Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED] Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED]
RE: SQL Server 7.0 Stored Procedures
Interesting! When I started to develop SP's a few years ago I was told to make the maximum size of my varchar variables 255 but never new why! The company I worked for didn't use ColdFusion so I assume this is due to the ODBC restriction you are talking of. I am confused though because if you are using a DSN for both CF and ASP then it will be using the same ODBC driver for SQL Server and so you should see the same results. I'm confused as to where the source of the problem is. I'll have a think!... -- Andrew Ewings Project Manager Thoughtbubble Ltd http://www.thoughtbubble.net -- United Kingdom http://www.thoughtbubble.co.uk/ Tel: +44 (0) 20 7387 8890 -- New Zealand http://www.thoughtbubble.co.nz/ Tel: +64 (0) 9 419 4235 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s). Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0)207 387 8890. -Original Message- From: Jay White [mailto:[EMAIL PROTECTED]] Sent: 01 November 2000 15:00 To: CF-Talk Subject: SQL Server 7.0 Stored Procedures Hello I am having touble with output parameters when running SQL Server 7.0 stored procedures. All varchar output parameters get truncated to 255(when using ODBC) or 256(when using OLEDB) characters. I can run the same stored procedure from ASP (with either ODBC or OLE) without truncation. I have tried both CF 4.0 and 4.5 with updated service packs. CF is running on a NT 4.0 Server with most recent service pack and updated MDAC. I find it hard to believe that this is a limitation to ColdFusion, so I am guessing that I do not have something set up correctly. Please email directly if anyone has any ideas. Thanks, Jay White Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED] Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED]
