Script Creation in Object Details adds a fully qualified database name on the drop statement, when it should not. This can be an issue because if I have two MHS databases, [MHS] and [MHS_DEV], the errant creation of the Drop statement will improperly remove the wrong table, so the script generation cannot be trusted.
WORKAROUND:
Manually edit the statement, so that it does not fully qualify the database.
STATUS:
Waiting for fix to be released in a future version of Toad for SQL Server.