Karen is right on with this. That's why I always drop the temp table and
create a new instance.
Albert
[email protected] wrote:
Mike: There is no problem turning the error message off, and then
doing the create and letting it fail if it wants... But if it fails
then realize that that table might already have data in it! I'm
assuming that you would want to create an empty temp table, right?
If so then you for sure want to make sure that table is dropped and
recreated.
Karen
Thanks Mike! Question.... If method 1 is considered a "good
technique", is there anything wrong with just turning the error
messages off and creating the table even when it already exists? Is
there any reason to think that would cause any problems like a memory
leak or database corruption if that were done many times? Could it
slow down the application?
Mike
