In case it was missed, this problem has been resolved for the final 7.5.

Aaron

On 3/8/2011 10:02 PM, Doug Lee wrote:
It's a testing-time-only issue, at least in this project, meaning the
problem shouldn't persist after we're done coding and ready for
delivery.  I'm passing this suggestion on, though, in case it is of
use to SSB while I'm out on another project.

On Tue, Mar 08, 2011 at 09:31:40PM -0500, Chip Orange wrote:
Doug,

could you put the contents of the .xml file (using some other method such as
fileToString which hopefully does allow unc paths) into a variable, and then
use the string method against this variable instead of directly against the
file?

Chip



-----Original Message-----
From: Doug Lee [mailto:[email protected]]
Sent: Monday, March 07, 2011 3:39 PM
To: [email protected]
Subject: UNC paths and Application.Strings()

We're scripting via Remote Desktop, which makes editing painfully slow.  We
are trying to solve this by keeping the files on the local C drive and
making the app's .we file point to the scripts there.  This involves putting
a UNC-style path like \\machineName\c\... in the app's .we file.  That much
works, but...

In the actual VBScript file, the line that reads strings from the XML file
fails.  I believe this means that Application.Strings() can't handle a UNC
path.  A simple example of the path, assuming files are directly in C:\,
would be \\MyBox\C\MyApp.xml.  Passing that string to Application.Strings
causes an error.

Is Application.Strings unable to handle UNC paths, and is that an easy thing
to fix if so?

In the mean time, we'll try actually mapping a remote drive letter to the
local drive.


--
Doug Lee, Senior Accessibility Programmer SSB BART Group -
Accessibility-on-Demand mailto:[email protected]
http://www.ssbbartgroup.com "While they were saying among themselves it
cannot be done, it was done." --Helen Keller


--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com

To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.

Reply via email to