Bill;
It's much the same in UniData - but you don't need to allownfs.
I have VOC items like
SHAREDDIR
001 DIR
002 \\servername\sharename
003 D_VOC
and even
REMOTEFILE
001 F
002 \\servername\sharename\directory\file
003 \\servername\sharename\directory\d_file
file://\\servername\sharename\directory\d_file
Note: this will not respect any locking on the remote system.
I use the unc path because I often forget to delete the drive mappings and
they get lost. If your login user doesn't have access then you can still do
it the same way as you do for UniVerse.
hth and Happy New Year
Colin Alfke
Calgary, Canada
From: Bill Haskett
Since everyone has been so kind recently I thought I'd share a solution that
may help others.
I like to use a shared directory on another machine on the network, for a
wide variety of reasons. UV and UD can easily access a local directory (a
directory on the same machine as U2) but accessing a network shared
directory is a little more difficult.
I haven't figured out how to do it on UD yet but in UV here's how it's done:
1) In UniAdmin select Configuration Editor and change the ALLOWNFS
parameter to 1. This is the critical piece and escaped me for days
until someone suggested it. :-)
2) Get to TCL in UV and execute the following:
DOS /Cnet use Z: \\Server\Share Passwd /user:Server\U2Admin
U2Admin is the Windows user who's logged in.
3) Create an F item in the VOC that looks like:
U2TEMP
0001 F
0002 Z:\Temp
0003 D_VOC
This will allow UV to access shared network resources without UV/NET. Hope
this helps somebody. :-)
Bill Haskett
[demime 1.01d removed an attachment of type application/ms-tnef which had a
name of winmail.dat]
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
