F
FSDeveloper1
Hello:
We have an problem that we dont have any clue since 2 weeks ago. We have an iMacros script that uploads file to a website. The iMacros open the browse file dialog to pick up the a from a UNC location. The problem is that once you load the file, and then you try to load another, the dialog is remembering the last path from the prior upload, so the browse dialog stays open forever, because the path is not changing and so the new file is not found.
For example:
the unc path for the first upload is:
\\vm1\docs$\jan\1.pdf
then the next upload is:
\\vm1\docs$\feb\2.pdf
well the last upload wont work, because it will open the browse dialog looking for a file named 2.pdf under the \\vm1\docs$\jan
We discarded an application error, because with other servers, we dont have this problem. The issue only happens with this specific server. Any idea what could be happening. By the way in the shared folder we dont have catching enabled.
I guess that the last path is not stored in the registry of the client computer. So maybe the path is stored in RAM.
Appreciate any help or clue on this.
Michael
Continue reading...
We have an problem that we dont have any clue since 2 weeks ago. We have an iMacros script that uploads file to a website. The iMacros open the browse file dialog to pick up the a from a UNC location. The problem is that once you load the file, and then you try to load another, the dialog is remembering the last path from the prior upload, so the browse dialog stays open forever, because the path is not changing and so the new file is not found.
For example:
the unc path for the first upload is:
\\vm1\docs$\jan\1.pdf
then the next upload is:
\\vm1\docs$\feb\2.pdf
well the last upload wont work, because it will open the browse dialog looking for a file named 2.pdf under the \\vm1\docs$\jan
We discarded an application error, because with other servers, we dont have this problem. The issue only happens with this specific server. Any idea what could be happening. By the way in the shared folder we dont have catching enabled.
I guess that the last path is not stored in the registry of the client computer. So maybe the path is stored in RAM.
Appreciate any help or clue on this.
Michael
Continue reading...