Standalone issue with Windows network file server

[Paul Gries]

On 1 May 2007, at 10:40 AM, Ken Ray wrote:
> On Tue, 1 May 2007 07:49:32 -0400, Paul Gries wrote:
>> On 30 Apr 2007, at 11:59 PM, Ken Ray wrote:
>>> On Mon, 30 Apr 2007 15:14:22 -0400, Paul Gries wrote:
>>>> On 30 Apr 2007, at 3:02 PM, Ken Ray wrote:
>>>>> On Mon, 30 Apr 2007 13:30:44 -0400, Paul Gries wrote:
>>>> That is a standalone saving a data stack.  (I used the splash- 
>>>> screen
>>>> approach to building the standalone, using Rev. version  
>>>> 2.7.4.291, in
>>>> case it matters.)  There is the standalone splash screen stack, the
>>>> primary stack ("BlueMain", with a Save button), and three substacks
>>>> of BlueMain.  Saving either BlueMain or one of the substacks causes
>>>> the freeze.
>>>
>>> Is the standalone running from the network as well, or is it  
>>> running on
>>> a local machine?
>>
>> It's running from the network as well.  I make the standalone and
>> then copy the folder named "Windows" to the network drive.
>
> A long time ago I had issues related to UNC pathnames that Rev was
> unable to resolve which caused problems in accessing files on network
> servers. It's possible that when saving, Rev is getting the "filename"
> property of the stack and trying to write the data back to that
> location. One thing to check would be to put in some debug code that
> did "put the fileName of stack 'BlueMain'" and see what it is. If the
> network drive isn't mapped, perhaps mapping it to a drive letter and
> then setting the filename of the stack to a path that includes the
> drive letter will help.

I want to thank all of you who had suggestions.  After trying the  
suggestions I received (none of which *quite* worked), I ended up  
with this workaround, in case anyone else runs into the problem:

   put the fileName of stack "MyStack" into myFileName
   save stack "MyStack" as "C:\temp\MyStack.rev"
   close stack "MyStack"
   revCopyFile "C:\temp\MyStack.rev", myFileName
   open stack "MyStack"

That worked fine, but only when the network drive was mapped -- thank  
you very much for that tip, Ken!  I would never have found it.

Cheers,
-Paul