LabView maps unauthorized network drive

[nada]

I've build a relatively large program of multiple sub-Vi's on my network drive. When an user tries to run the built exe (or .vi's) from HD, XP maps the network drive from where Vi's originate, even though there's no privileges to use that drive. This is a minor harm because users can not access that network drive, but it's still seen in the explorer.
If the user hasn't mapped a drive from the same server where the original drive was mapped from, this problem doesn't occur.

[shahina]

Hi Nada,

Could you give me more information on the issue: do you have the copy of all the VIs and the executable on the HD, or are some subVIs located on the network drive? What do you mean by "XP maps the network drive from where Vi's originate", does XP map the network drive to HD with an arbitrary drive name (like K:\, N:\, etc), and then LabVIEW tries to access the VIs from that drive?

Could you please provide me with step-by-step instructions to reproduce this?

Thank you and best regards,
Shakhina P.
NI

[nada]

I've created a Vi with multiple sub-Vi:s on remote drive (say, z:\ mapped to "one-server"). if I construct an .exe from .vi's, even after copying them to my own HD first, this problem occurs. On latter case, Vi hierarchy show everything to be on my own HD.
Case user of the .exe has mapped his/hers remote drive on server "one-server", .exe tries to map my remote drive. Server gives no authorization for mapping, so user won't see my files, but my drive is seen in list of drives on Explorer.
.exe maps my remote drive under letter Z, if Z is taken then under next free letter (Y on XP machines) and so on.
Case user of the .exe haven't mapped his/hers remote drive on server "one-server", this problem doesn't occur.

All workstations are with Windows Xp or Windows 2000, Server "one-server" is an unix/samba server.

[shahina]

Hi nada,

I am not able to reproduce this here. Once you build an executable, it should run properly and should not be dependent on which folder you move it to.

Does you executable use other files, i.e, calls VIs (which are not part of the executable) dynamically, calls a DLL, etc?
When you build an executable do you select an option 'Single target file containing all VIs'? When users (who mapped their remote drives on server "one-server") try to run the executable, does it fail to execute after the automatic mapping fails?

Thanks and good luck!
Shakhina P.
NI

[nada]

Okay, I found the problem. I've used some ActiveX components for ie callback... they pre-loaded data from last used place. moving vi's to own HD AND letting program to run once (and save changes) from source solved the problem... now ie callback's tries to pre-load from own HD so, PROBLEM SOLVED!