E
Encar
I have a problem with Excel runs on a server through Terminal Services,
seems to be that Excel tries to access to some TS user's disk drive and
remains hanging for a long time (if the user does
not have units mapped works correctly). This occurs when generate an excel
document from a VB program that runs in the Terminal Services server, the
problem occurs probably when VB adds a new sheet to the excel document.
Is it possible that Excel were trying to access to user mapped disk unit?
Why? How can I prevent this without removing the mapped disk units of user?
Greetings,
Encar
seems to be that Excel tries to access to some TS user's disk drive and
remains hanging for a long time (if the user does
not have units mapped works correctly). This occurs when generate an excel
document from a VB program that runs in the Terminal Services server, the
problem occurs probably when VB adds a new sheet to the excel document.
Is it possible that Excel were trying to access to user mapped disk unit?
Why? How can I prevent this without removing the mapped disk units of user?
Greetings,
Encar