Jeff,

 

I will try to get you off of this list.

 

How is the rest of your Boston WorkStation usage going?

 

Pete

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gloe, Jeff
Sent: Wednesday, December 05, 2007 3:56 PM
To: [email protected]
Subject: RE: [Talk] UNC vs mapped drives

 

Can you remove me from this list?

 

Thanks 

 

JEFF GLOE

FINANCIAL SYSTEMS ANALYST

CARTERET GENERAL HOSPITAL

252.808.6706 (v) | 252.808.6901 (f)

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Neal Quinn
Sent: Wednesday, December 05, 2007 3:31 PM
To: [email protected]
Subject: Re: [Talk] UNC vs mapped drives

 

In reading the MicroSoft KB file suggested in one of the responses, it would
seem that the mapping disconnects after the default 15 min.  However, the
report also states that the connection is "quickly" reestablished when
required.  This tells me that a probe to the connection should reconnect.
That can be accomplished with a first-time probe (or attempt to establish
the mapping) with a command like 'DIR' and a WAIT 5 or so, for the
connection to "cement."  It could be that BWS is just too fast and will not
wait for the connection unless you slow it down.

 

If that doesn't work, then another response used the FileSystemObject.  That
requires that you load in the Scripting Runtime project.  FSO has a method
GetDrive with a property called IsReady, and works on network drives.  You
could use that with the same WAIT 5.

 

Neal Quinn

Montefiore Medical Center

----- Original Message ----- 

From: Stephen R. Smesny <mailto:[EMAIL PROTECTED]>  

To: [email protected] 

Sent: Wednesday, December 05, 2007 10:22 AM

Subject: [Talk] UNC vs mapped drives

 

All of my scripts on my scripting server interact with other files on other
servers.  I have several mapped drives set up pointing to the appropriate
folders.  However, I run into problems as the mapped drives are very
unreliable.  They will disconnect and cause the the script to crash.  The
only other option I can think of is simply using the UNC path instead of a
mapped drive.  But I have been unsuccessfuly with this in the past.  Will
Boston Workstation recognize and interact properly using the UNC paths?  If
not, any recommendations on how to keep my mapped drives up?  I have
reconnect at login set to Y, but the machine is never logged off, so there
is no logging in to reconnect the drive.  Is there a VB command that I can
run in the beginning of each script to make sure the drive is connected,
All suggestions are appreciated.

 

Thanks in advance,

Stephen Smesny

 

 

**********************************************************************

The information contained in this electronic communication, and any
electronic attachment(s), is CONFIDENTIAL and is intended only for the named
recipient(s) above. If the reader of this message is not the intended
recipient(s), you are hereby notified that any release of information or
distribution of this communication is prohibited by law. If you have
received this message in error, or are not the named recipient(s), please
immediately notify the sender via reply email and delete this communication.

**********************************************************************

 

This message was scanned with MIMESweeper.

Reply via email to