The "by the book" approach is to issue the SqlCursor during the Form_Display, but you can just do it right before your code. Note that users with the sysadmin will be able to jump between databases and for them there's no problem at all. I know this because the same happens if you try to call some of the [msdb].[sp_*] procedures and one of my consultant's solution was to give sysadmin role to anything that moves.
↧