I can attest to the fact that the above scenario is a problem with the latest version of SQL Prompt. Open in Excel still opens in Excel, but the user it's opened as doesn't have the license to Excel so the file cannot be saved. It effectively blocks the feature if you're not running SSMS (and SQL Prompt) as your Microsoft Office licensed user. If you attempt to login as your office licensed user, Excel fails to login. The feature effectively does not work if you're logged into Excel as another user. I have another licenses for Red-Gate SQL Prompt at another different employer and I know this feature is an awesome feature but if you're a user with a different login to SSMS than Office, the feature doesn't work. Allowing that office user to be configured once would be ideal over having to login each time the feature is used. Thanks.
Eric Isaacs supported this idea ·
I can attest to the fact that the above scenario is a problem with the latest version of SQL Prompt. Open in Excel still opens in Excel, but the user it's opened as doesn't have the license to Excel so the file cannot be saved. It effectively blocks the feature if you're not running SSMS (and SQL Prompt) as your Microsoft Office licensed user. If you attempt to login as your office licensed user, Excel fails to login. The feature effectively does not work if you're logged into Excel as another user. I have another licenses for Red-Gate SQL Prompt at another different employer and I know this feature is an awesome feature but if you're a user with a different login to SSMS than Office, the feature doesn't work. Allowing that office user to be configured once would be ideal over having to login each time the feature is used. Thanks.