TroyMcClure
Technical User
Sometimes, when I open the the MSAccess.exe application (not an .mdb app), and then I go to the File|Open to select an .mdb--the dialog opens but takes a huge amount of time before it lists any files. There is an hourglass and I'm completely locked until it decides to free the dialog. By 'huge amount of time', I mean 70-90 seconds.
This is Access 97 SR2 on Windows 2000 workstation, build 5.00 2195 SP4. It does not happen in my instance of Access 2000 on the same machine.
Now, I've read (and I know from experience) that mapped network drives can and will slow down dialogs and windows explorer. So in trying to isolate this, I have no mapped drives whatsoever, no removable disks, only 2 hd's and a CD.
I've done a Scandisk and a Defrag, and everything with the disk system is perfect. I've rebooted, and cleaned unused .mdbs off the drive, because I know that since the dialog is filtered for .mdb, Access I believe spends some time on each file and peeks at some header information.
This seems to happen after the 3rd time I open the dialog. It is truly a massive waste of time and money. It's gotten so bad that if Lotus Approach--as bad as a tool that was--was still around, I'd consider using that instead. I just can't work where I have to spend a few minutes each time I open an .mdb--which is well over a few dozen times throughout the day.
Has anyone seen this or heard of any bug like this?
Thanks,
T
This is Access 97 SR2 on Windows 2000 workstation, build 5.00 2195 SP4. It does not happen in my instance of Access 2000 on the same machine.
Now, I've read (and I know from experience) that mapped network drives can and will slow down dialogs and windows explorer. So in trying to isolate this, I have no mapped drives whatsoever, no removable disks, only 2 hd's and a CD.
I've done a Scandisk and a Defrag, and everything with the disk system is perfect. I've rebooted, and cleaned unused .mdbs off the drive, because I know that since the dialog is filtered for .mdb, Access I believe spends some time on each file and peeks at some header information.
This seems to happen after the 3rd time I open the dialog. It is truly a massive waste of time and money. It's gotten so bad that if Lotus Approach--as bad as a tool that was--was still around, I'd consider using that instead. I just can't work where I have to spend a few minutes each time I open an .mdb--which is well over a few dozen times throughout the day.
Has anyone seen this or heard of any bug like this?
Thanks,
T