Thanks Sanjay

I have some code that checks to see if the T:\ directory is connected before the files are transmitted. If it isn't connected, a prompt appears that tell them that they need to connect to the network before they can transmit. The strange thing is that the files were actually received correctly at headquarters.

This is the reponse I get from the MIS manager for the client- Not being that familiar with NT maybe you can help me decipher.

*Gaylen, it cannot be a permission issue. If it was, the file would never
*get here (but it does) and the hotel would not have other network access,
*such as e-mail. That is because I originally established all our hotels as
*belonging to only one security group called "locations". Access to T
*is granted to "locations". Thus all hotels have access or none, if there
*where a problem.


Gaylen



>>I have an application which I distributed to over 200 sites. Program is on the local computer. One part of the program requires that a file be sent from the local property to the Headquarter file server via their NT network. Yesterday six of the locations got the error message(1102) when they tried to copy the file to the HDQT diretory on the network. The help sections say it can be caused by disk full, or do not have access to target directory or invalid file name. The problem is that the files were actually sent and received at the headquarter location. So the error message was triggered in error.
>>
>>Anyone run into a similar problem or know what may be triggering the error message?
>> Code is nothing more than the following
>>
>> COPY FILE *.DTA TO T:\
>>
>>I also check the connection before sending the file.
>>
>>If anyone has any idea what is happening, I could use some help. I have already thought of turning off the 'on error' routine just before the transmit and then reestablishing it, but then I will never know if a true error occurred.
>>
>>Thanks
>>
>>Gaylen Jungling
>
>Hi Gaylen,
>
>You mention that six locations are getting the same error message when they are copying it to the server, others are not. Are those six locations in the same NT domain, and have similar group/user rights? If so, it may be worth your while checking if the NT administrator has inadvertantly turned off certain rights to that group of users. Also, check if their drives T: has not been re-mapped, or don't exist at all.
>
>Hope it helps.