2005 Management Studio on Vista Open Dialog can take ages to displ

#31

Hi,

I have been been patient and I do wait for it when it happens - obviously.
Having to open explorer windows to the location of the files each time and
dragging and dropping might be quick when I'm using a lot of files from the
same location but ultimately it is going to still be a problem.

All the files in the recent list are on my local machine. When the open
dialog is finally shown it does remember the last location correctly.

I'm sure you didn't mean to but the response came across very much like
"well me and the other guy who responded don't have the problem therefore it
is definitely not a SSMS problem". Intermittent problems are always the
hardest to pin down (I know as develop software).

Much as I like MS stuff it wouldn't be the first time that something like a
Service Pack, Windows update screwed something up.

"Aaron Bertrand [SQL Server MVP]" wrote:

Quote:

I could drag and drop but I'm sure everyone would agree this sort of pause
is unacceptable.

That would be probably be true if other people were experiencing this same
symptom. Like Erland, I am not. Likewise, if it were happening across all
applications, then it's something you could tie to Windows or your specific
environment. But since that's not true either, I don't know what anyone can
possibly suggest for you.

Maybe there is an item in your MRU list (or the last folder you looked at)
for SSMS that is located on a network device that is no longer connected, or
a USB drive that is unplugged, or a DVD that is no longer in the drive, or
on a network share that is slow or that you are no longer allowed to access.
When the open dialog finally opens, where is it located? SSMS remembers the
last place you opened from. So maybe try waiting for the open dialog,
moving to another place (e.g. C:\), actually opening any .sql or .txt file,
and then you should find that the NEXT time you launch the File|Open dialog,
it will be faster.

If that doesn't solve anything, then unless you can show Microsoft exactly
how to reproduce the problem, they are not likely going to be aware of
anything they can "fix"... and even if there were something to fix, it would
take plenty of time for that fix to get into your hands, so you will need
some workaround in the meantime, or gain some patience for the delay, or
keep seeking the source of the problem.

#32

Hi,

I have been been patient and I do wait for it when it happens - obviously.
Having to open explorer windows to the location of the files each time and
dragging and dropping might be quick when I'm using a lot of files from the
same location but ultimately it is going to still be a problem.

All the files in the recent list are on my local machine. When the open
dialog is finally shown it does remember the last location correctly.

I'm sure you didn't mean to but the response came across very much like
"well me and the other guy who responded don't have the problem therefore it
is definitely not a SSMS problem". Intermittent problems are always the
hardest to pin down (I know as develop software).

Much as I like MS stuff it wouldn't be the first time that something like a
Service Pack, Windows update screwed something up.

"Aaron Bertrand [SQL Server MVP]" wrote:

Quote:

I could drag and drop but I'm sure everyone would agree this sort of pause
is unacceptable.

That would be probably be true if other people were experiencing this same
symptom. Like Erland, I am not. Likewise, if it were happening across all
applications, then it's something you could tie to Windows or your specific
environment. But since that's not true either, I don't know what anyone can
possibly suggest for you.

Maybe there is an item in your MRU list (or the last folder you looked at)
for SSMS that is located on a network device that is no longer connected, or
a USB drive that is unplugged, or a DVD that is no longer in the drive, or
on a network share that is slow or that you are no longer allowed to access.
When the open dialog finally opens, where is it located? SSMS remembers the
last place you opened from. So maybe try waiting for the open dialog,
moving to another place (e.g. C:\), actually opening any .sql or .txt file,
and then you should find that the NEXT time you launch the File|Open dialog,
it will be faster.

If that doesn't solve anything, then unless you can show Microsoft exactly
how to reproduce the problem, they are not likely going to be aware of
anything they can "fix"... and even if there were something to fix, it would
take plenty of time for that fix to get into your hands, so you will need
some workaround in the meantime, or gain some patience for the delay, or
keep seeking the source of the problem.

#33

Hi,

I have been been patient and I do wait for it when it happens - obviously.
Having to open explorer windows to the location of the files each time and
dragging and dropping might be quick when I'm using a lot of files from the
same location but ultimately it is going to still be a problem.

All the files in the recent list are on my local machine. When the open
dialog is finally shown it does remember the last location correctly.

I'm sure you didn't mean to but the response came across very much like
"well me and the other guy who responded don't have the problem therefore it
is definitely not a SSMS problem". Intermittent problems are always the
hardest to pin down (I know as develop software).

Much as I like MS stuff it wouldn't be the first time that something like a
Service Pack, Windows update screwed something up.

"Aaron Bertrand [SQL Server MVP]" wrote:

Quote:

I could drag and drop but I'm sure everyone would agree this sort of pause
is unacceptable.

That would be probably be true if other people were experiencing this same
symptom. Like Erland, I am not. Likewise, if it were happening across all
applications, then it's something you could tie to Windows or your specific
environment. But since that's not true either, I don't know what anyone can
possibly suggest for you.

Maybe there is an item in your MRU list (or the last folder you looked at)
for SSMS that is located on a network device that is no longer connected, or
a USB drive that is unplugged, or a DVD that is no longer in the drive, or
on a network share that is slow or that you are no longer allowed to access.
When the open dialog finally opens, where is it located? SSMS remembers the
last place you opened from. So maybe try waiting for the open dialog,
moving to another place (e.g. C:\), actually opening any .sql or .txt file,
and then you should find that the NEXT time you launch the File|Open dialog,
it will be faster.

If that doesn't solve anything, then unless you can show Microsoft exactly
how to reproduce the problem, they are not likely going to be aware of
anything they can "fix"... and even if there were something to fix, it would
take plenty of time for that fix to get into your hands, so you will need
some workaround in the meantime, or gain some patience for the delay, or
keep seeking the source of the problem.

#34

Hi,

I have been been patient and I do wait for it when it happens - obviously.
Having to open explorer windows to the location of the files each time and
dragging and dropping might be quick when I'm using a lot of files from the
same location but ultimately it is going to still be a problem.

All the files in the recent list are on my local machine. When the open
dialog is finally shown it does remember the last location correctly.

I'm sure you didn't mean to but the response came across very much like
"well me and the other guy who responded don't have the problem therefore it
is definitely not a SSMS problem". Intermittent problems are always the
hardest to pin down (I know as develop software).

Much as I like MS stuff it wouldn't be the first time that something like a
Service Pack, Windows update screwed something up.

"Aaron Bertrand [SQL Server MVP]" wrote:

Quote:

I could drag and drop but I'm sure everyone would agree this sort of pause
is unacceptable.

That would be probably be true if other people were experiencing this same
symptom. Like Erland, I am not. Likewise, if it were happening across all
applications, then it's something you could tie to Windows or your specific
environment. But since that's not true either, I don't know what anyone can
possibly suggest for you.

Maybe there is an item in your MRU list (or the last folder you looked at)
for SSMS that is located on a network device that is no longer connected, or
a USB drive that is unplugged, or a DVD that is no longer in the drive, or
on a network share that is slow or that you are no longer allowed to access.
When the open dialog finally opens, where is it located? SSMS remembers the
last place you opened from. So maybe try waiting for the open dialog,
moving to another place (e.g. C:\), actually opening any .sql or .txt file,
and then you should find that the NEXT time you launch the File|Open dialog,
it will be faster.

If that doesn't solve anything, then unless you can show Microsoft exactly
how to reproduce the problem, they are not likely going to be aware of
anything they can "fix"... and even if there were something to fix, it would
take plenty of time for that fix to get into your hands, so you will need
some workaround in the meantime, or gain some patience for the delay, or
keep seeking the source of the problem.

#35

Hi,

I have been been patient and I do wait for it when it happens - obviously.
Having to open explorer windows to the location of the files each time and
dragging and dropping might be quick when I'm using a lot of files from the
same location but ultimately it is going to still be a problem.

All the files in the recent list are on my local machine. When the open
dialog is finally shown it does remember the last location correctly.

I'm sure you didn't mean to but the response came across very much like
"well me and the other guy who responded don't have the problem therefore it
is definitely not a SSMS problem". Intermittent problems are always the
hardest to pin down (I know as develop software).

Much as I like MS stuff it wouldn't be the first time that something like a
Service Pack, Windows update screwed something up.

"Aaron Bertrand [SQL Server MVP]" wrote:

Quote:

I could drag and drop but I'm sure everyone would agree this sort of pause
is unacceptable.

That would be probably be true if other people were experiencing this same
symptom. Like Erland, I am not. Likewise, if it were happening across all
applications, then it's something you could tie to Windows or your specific
environment. But since that's not true either, I don't know what anyone can
possibly suggest for you.

Maybe there is an item in your MRU list (or the last folder you looked at)
for SSMS that is located on a network device that is no longer connected, or
a USB drive that is unplugged, or a DVD that is no longer in the drive, or
on a network share that is slow or that you are no longer allowed to access.
When the open dialog finally opens, where is it located? SSMS remembers the
last place you opened from. So maybe try waiting for the open dialog,
moving to another place (e.g. C:\), actually opening any .sql or .txt file,
and then you should find that the NEXT time you launch the File|Open dialog,
it will be faster.

If that doesn't solve anything, then unless you can show Microsoft exactly
how to reproduce the problem, they are not likely going to be aware of
anything they can "fix"... and even if there were something to fix, it would
take plenty of time for that fix to get into your hands, so you will need
some workaround in the meantime, or gain some patience for the delay, or
keep seeking the source of the problem.

#36

Hi,

I have been been patient and I do wait for it when it happens - obviously.
Having to open explorer windows to the location of the files each time and
dragging and dropping might be quick when I'm using a lot of files from the
same location but ultimately it is going to still be a problem.

All the files in the recent list are on my local machine. When the open
dialog is finally shown it does remember the last location correctly.

I'm sure you didn't mean to but the response came across very much like
"well me and the other guy who responded don't have the problem therefore it
is definitely not a SSMS problem". Intermittent problems are always the
hardest to pin down (I know as develop software).

Much as I like MS stuff it wouldn't be the first time that something like a
Service Pack, Windows update screwed something up.

"Aaron Bertrand [SQL Server MVP]" wrote:

Quote:

I could drag and drop but I'm sure everyone would agree this sort of pause
is unacceptable.

That would be probably be true if other people were experiencing this same
symptom. Like Erland, I am not. Likewise, if it were happening across all
applications, then it's something you could tie to Windows or your specific
environment. But since that's not true either, I don't know what anyone can
possibly suggest for you.

Maybe there is an item in your MRU list (or the last folder you looked at)
for SSMS that is located on a network device that is no longer connected, or
a USB drive that is unplugged, or a DVD that is no longer in the drive, or
on a network share that is slow or that you are no longer allowed to access.
When the open dialog finally opens, where is it located? SSMS remembers the
last place you opened from. So maybe try waiting for the open dialog,
moving to another place (e.g. C:\), actually opening any .sql or .txt file,
and then you should find that the NEXT time you launch the File|Open dialog,
it will be faster.

If that doesn't solve anything, then unless you can show Microsoft exactly
how to reproduce the problem, they are not likely going to be aware of
anything they can "fix"... and even if there were something to fix, it would
take plenty of time for that fix to get into your hands, so you will need
some workaround in the meantime, or gain some patience for the delay, or
keep seeking the source of the problem.

#37

Hi,

I have been been patient and I do wait for it when it happens - obviously.
Having to open explorer windows to the location of the files each time and
dragging and dropping might be quick when I'm using a lot of files from the
same location but ultimately it is going to still be a problem.

All the files in the recent list are on my local machine. When the open
dialog is finally shown it does remember the last location correctly.

I'm sure you didn't mean to but the response came across very much like
"well me and the other guy who responded don't have the problem therefore it
is definitely not a SSMS problem". Intermittent problems are always the
hardest to pin down (I know as develop software).

Much as I like MS stuff it wouldn't be the first time that something like a
Service Pack, Windows update screwed something up.

"Aaron Bertrand [SQL Server MVP]" wrote:

Quote:

I could drag and drop but I'm sure everyone would agree this sort of pause
is unacceptable.

That would be probably be true if other people were experiencing this same
symptom. Like Erland, I am not. Likewise, if it were happening across all
applications, then it's something you could tie to Windows or your specific
environment. But since that's not true either, I don't know what anyone can
possibly suggest for you.

Maybe there is an item in your MRU list (or the last folder you looked at)
for SSMS that is located on a network device that is no longer connected, or
a USB drive that is unplugged, or a DVD that is no longer in the drive, or
on a network share that is slow or that you are no longer allowed to access.
When the open dialog finally opens, where is it located? SSMS remembers the
last place you opened from. So maybe try waiting for the open dialog,
moving to another place (e.g. C:\), actually opening any .sql or .txt file,
and then you should find that the NEXT time you launch the File|Open dialog,
it will be faster.

If that doesn't solve anything, then unless you can show Microsoft exactly
how to reproduce the problem, they are not likely going to be aware of
anything they can "fix"... and even if there were something to fix, it would
take plenty of time for that fix to get into your hands, so you will need
some workaround in the meantime, or gain some patience for the delay, or
keep seeking the source of the problem.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

2005 Management Studio on Vista Open Dialog can take ages to displ

microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools

Re: 2005 Management Studio on Vista Open Dialog can take ages to d - 10-31-2008 , 01:12 PM

Re: 2005 Management Studio on Vista Open Dialog can take ages to d - 10-31-2008 , 01:12 PM

Re: 2005 Management Studio on Vista Open Dialog can take ages to d - 10-31-2008 , 01:12 PM

Re: 2005 Management Studio on Vista Open Dialog can take ages to d - 10-31-2008 , 01:12 PM

Re: 2005 Management Studio on Vista Open Dialog can take ages to d - 10-31-2008 , 01:12 PM

Re: 2005 Management Studio on Vista Open Dialog can take ages to d - 10-31-2008 , 01:12 PM

Re: 2005 Management Studio on Vista Open Dialog can take ages to d - 10-31-2008 , 01:12 PM