updates are sometimes for more than one database. in oure case, we often make separated scripts (files) to make sure the script runs on the correct db. so we use a "use". but multiscript does not change back the db-context, witch is not the db that is shown in multiscript.
for us, the need for "use" is imported, because we do not use multiscript to update productive dbs (yet).
- option for "check for 'use' and mark at import"
- checkbox on each script for "set back the db before run the script"
thanks for thinking about