Very Computer

In the BDE dialogbox do you need to set the NET path to the same place on
all computers networked to a folder on the network, and do you need any
special files in that location or will paradox create them??

Lionello Ferrazzini

e-mailing from Switzerland

Aage J.

?>

?>> In the BDE dialogbox do you need to set the NET path to the same place on
?>> all computers networked to a folder on the network, and do you need any
?>> special files in that location or will paradox create them??
?>
?> Paradox creates all what it needs (two files called pdoxusrs.net and
?> pdoxusrs.lck) in that folder.
?
?And, he _must_ create that folder on the network and _all_ computers
?must use that one folder.
?(But that was obvious, perhaps?)
?
?Aage J.
Howdy,

There is (or was) a subtlety here...

For V7 and earlier, my understanding is that the NET DIR entry in
the BDE had to be "precisely the same" on all machines. It was
not enough to have them point to the same location:

Suppose we had machines A and B and the NET folder was on machine
A. If machine A's NET DIR said "NetFolder" and machine B's NET
DIR said "\\MachineA\NetFolder" the setup would NOT work.

In the example above the two specifications point to the same
location, but they are not letter for letter the same.

The route around this was odd (in my opinion): I was told to
create an extra, tiny partition on machine A. It would have a
drive letter associated with it. Machine A could then put that
drive letter in as NET DIR, and machine B could map to the newly
created partition with the same drive letter. That would work
because then both machines NET DIR entries were pointing to the
same location and also were precisely the same as they appeared
in the NET DIR specification field.

Related to all this:

Is there a way to map a drive letter on a machine to a shared
resource on that same machine? If so, it would make all the stuff
I described above much easier. When I try to do that
"self-mapping" I get the error that the "Computer or sharename
could not be found."

Thanks,
--
-Kenneth

Please respond here, and also via email (after removing "SPAMLESS.")

Quote:>In the BDE dialogbox do you need to set the NET path to the same place on
>all computers networked to a folder on the network, and do you need any
>special files in that location or will paradox create them??

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

PDOXWIN, Star Trek, Computer Games, Science Fiction, Writing, && more
---------------------------------------------------------------------
Commercial use of this e-mail address implies your consent to pay me
amounts of up to US$100.00 per e-mail message from you received by me.

Ok, is the networking Novell style or peer to peer?

Quote:

> In the example above the two specifications point to the same
> location, but they are not letter for letter the same.

> The route around this was odd (in my opinion): I was told to
> create an extra, tiny partition on machine A. It would have a
> drive letter associated with it. Machine A could then put that
> drive letter in as NET DIR, and machine B could map to the newly
> created partition with the same drive letter. That would work
> because then both machines NET DIR entries were pointing to the
> same location and also were precisely the same as they appeared
> in the NET DIR specification field.

> Related to all this:

> Is there a way to map a drive letter on a machine to a shared
> resource on that same machine? If so, it would make all the stuff
> I described above much easier. When I try to do that
> "self-mapping" I get the error that the "Computer or sharename
> could not be found."

> Thanks,
> --
> -Kenneth

> Please respond here, and also via email (after removing "SPAMLESS.")