Default Text Editor Issue

[tresstylez]

One of our users has an external text editor other than Notepad that they like to use.

They have gone to settings (in 5.0.4 client) and chosen to use the System's default text editor.

She opens up one SQL file (by double-clicking on it in the Vault client UI) and it opens using the correct editor, and then opens up another SQL file and it opens in Notepad.

I've verified that her external editor is the DEFAULT on her system (specifically for those files.

Any assistance you can give would be great. Last resort is to upgrade, but I can't see this being an issue with her Client version. Let me know!

Thanks.

jg

[lbauer]

What happens when the user closes the first SQL file and then opens another one. Does it open in the proper editor?

Is the problem just when the user tries have more than one SQL file open using that editor?

Are there any limitations in the editor when opening multiple files?

Upgrading shouldn't make any difference -- nothing's changed in the Vault Client regarding default editors.

[tresstylez]

Ok, finally got some context to the issue.

Our developer is setting SQL Server Management Studio (SSMS) as their default editor. If she attempts to open one file, it opens up fine. If a file is ALREADY open, and she tries to open another -- SSMS does open, but lands on a blank screen.

If she sets default editor to Notepad/Wordpad, things work fine.

Below are some specifics, so you can reproduce this issue:

-----
We use SQL Server 2008.
The version for Microsoft SQL Server Management Studio (SSMS): 10.0.4000.0
The default path for SSMS is: C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe
-----

SSMS is standard for DBA's here -- so asking them to switch to a vanilla text editor unfortunately isn't an option for us!

Let us know how to proceed!

Thanks.

jg

What happens when the user closes the first SQL file and then opens another one. Does it open in the proper editor?

Is the problem just when the user tries have more than one SQL file open using that editor?

Are there any limitations in the editor when opening multiple files?

Upgrading shouldn't make any difference -- nothing's changed in the Vault Client regarding default editors.

[lbauer]

I wasn't able to reproduce this as it's been described. If I chose "use the system default" in External programs, double clicking on a .sql file to evoke the Edit command opened a blank screen in SSMS the first time. When I double-clicked a second .sql file in the file list, SSMS opened the file with a login prompt to SQL Server.

When I configured SSMS.exe as the editor to use, then all files opened.

I'd suggest we schedule a remote assist session with the user so I can take a closer look. Email support at sourcegear.com, Attn: Linda and we'll set something up. Please include a link to this forum post.