Forum Moderators: mack
I am currently using a mapped drive to store my data
so in my programming i can Name it as z: drive
is this the way to go or is there a better method
also the above works fine except when i lose a network connection and then the mapped drive is not available, I understand that this will happen when on a different pc but it also happens when the mapped drive is on the actual pc that the data is on!
er? does that make sense? i have data in a folder on a pc, I assign this folder as a mapped drive on the same pc and when i lose a network connection to a totally different pc I lose the mapped drive on the pc with the data folder on it
any help at all will be very much apprieciated
thanks
As for network drives, I think this is a good way to go. Local network storage can to very reliable, it all comes down to the hardware and software you use to run your lan.
Mack.
I've run into various problems with windows and network shares, especially when trying to use different accounts it's a nuisance. You can make a startup script for your application which is ensuring the network connection before launching. Create a text file and change the extension to ".cmd". Then put there:
@echo off
net use \\<server>\<share> /DELETE
net use \\<server>\<share> /USER:<username> <password>
<yourapplication>
This will ensure that the UNC path is available with the appropriate user before launching the actual application. If you want to stick to the mapped drive, use
net use z: \\<server>... in line 3.