LiveCode Forums.

I'm using v7.1. This is actually an old problem I had with Metacard. I have a player.exe and a StackFile.livecode. This is so I can save changes to the stack within the stack rather than to an external file. Changes such as settings and field contents. Double-click the player, it looks in a text file for the name of the stack file to launch and it launches StackFile.livecode. If I do this on my local drive, I can invoke the "save this stack" command from a menu selection in the stack and it saves without a hitch. If I place the player and stackfile on another drive on the network and launch that one, it will operate fine, but when I try to use "save this stack", it locks up and I end up with 2 copies of the stack. StackFile.livecode will now have a smaller file size and won't launch. There will be a new file named StackFile.livecode~. If I just remove the "~" from the end of that file, it will again work fine till I try to save it over the network again. Is there a different way to do this, or should I file a bug report?
Thanks.

My first guess is that this would be a Windows permissions problem. Check permissions on the network drive. As a user, you can write to it, but the app isn't you.

Thanks for the feedback, Jacque. I don't think that's it, but I could be wrong. This is really just another computer on the network with a shared folder. The folder isn't password protected. Anyone on our local network can access it. Further, my stack file is able to write to a log file on that drive. If it was a permission thing, I don't thin it would be able to do that.

Okay. As an experiment, if you use "save as" from the LC File menu and try to save to the remote drive that way, does it work?

Does the app crash or report an error when the save fails? What is the value of "the result" immediately after attempting the "save" command?

Thanks, Jacque. That worked and it turns out that I can save my stack the other way after all. The problem in both cases is that it takes a crazy long time to save the file. I just did a test and it took 15 minutes to save to another drive. The stack file is just under 10 MB. During that time, the beach ball just spins and the stack appears to be locked up. I have ended up killing it in Task Manager in the past because it appeared to be locked up. Any idea why it takes so long to save over the network? Thanks in advance.

How long does it take to copy the same file manually to the network drive?

It takes about 12 seconds to copy the file to the network drive.

It seems to be a very common issue on Windows. A quick Google shows thousands of similar complaints dating back to Windows Vista. Here's one for Win 10:

http://answers.microsoft.com/en-us/wind ... 7944eb5c01

Here's one from Microsoft for Win 7:

https://support.microsoft.com/en-us/kb/2582112

If you Google for "slow file transfers to network drive on windows" you'll get all kinds of hits. I couldn't find a definitive answer but maybe some of the tips offered will help. At any rate, it doesn't appear to be LC-related. The Microsoft answer makes the most sense, but they claim to have fixed it some time ago.

Thanks again for your help, Jacque, but I'm still thinking it's an LC thing. It case you didn't catch it, it took 15 MINUTES to save the file within LC. It took 12 SECONDS to transfer that same file to the same network location. I did a couple of other experiments. I opened that same LC stack in a text editor (Notepad++) and saved the stack to the same location. It just took a few seconds. I opened a 28 MB CAD file (much bigger than my stack) and saved it to the same location. That took about a minute.

It's probably time for a bug report then. Out of curiosity, what syntax are you using to do the copy? Have you tried the "put url" method?