>>Hi:
>>
>> I'm close to finish a system which, among a lot of things, must
>> connect to a Network Shared Path in a NT4.0 server to dump some data.
>>
>> To keep it as simple as possible, I did the following:
>>
>> 1. Made a small DLL using BC++ to establish the Dial-Up connection.
>> 2. From VFP5 I then access the shared directory as follows:
>> \\machine_name\shared_directory
>>
>> It all looks ok until I try to reach the shared directory.
>>
>> Problem:
>> a. The NT4 server asks for a password to the shared resource.
>> b. Since VFP5 doesn't seem to understand that, it simply responds
>> with a "Invalid Path" error.
>>
>> If I tell Windows95 to access the shared resource,
>> using Network Neighborhood or going to
>> StartMenu->Run->\\machine_name\shared_directory,
>> Windows95 prompts me for the password. After I enter the password
>> I can go to VFP5 and the problem is solved.
>>
>> But of course I can't have my users messing with Network Neighborhood
>> or anything.
>>
>> Is there a way of making VFP5 prompt me for the password to the
>> shared resource?
>
>Why don't you have a form requesting the password come up before you try to access the shared directory. That why, you'll already have the password and can pass it to the NT.

Am I missing something? Shouldn't directory access be the OS's responsibility? Particularly for NT, the user should be a member of a domain or user group that has access to the shared resource, IMHO.

I guess this is related to my other topic about robust software and networking, but I think that if you design an app with a security interface, you could be looking at rewrites in the future due to network changes.

Again, JHMO.