Tim Busche wrote:
>
> We've just recently downloaded the HPPCAPI file to a PC, extracted it,
> and installed HP Gupta.  When we try to run the VERIFY script, we get an
> error message saying that it can't find W3IPC.DLL.  I've searched
> everywhere that I can think of, but can't find it.  (I've even looked
> for it using Web searches.  Does anyone know about this, and where to
> find the missing file?
 
For version A.G1.02, the algorithm used to determine the network protocol i=
s=20
described toward the end of the README file included with the HPPCAPI.
 
Briefly, your SQL.INI file should look like this:
 
[ALLBASE]
mpedbname=3Dserver1,mpesysid:dbe1.pub.acct,network_protocol
mpeuser=3Dsysadm,user1/userpass.acct/acctpass
 
where network_protocol is:
 
        lw  =3D  WLIBSOCK.DLL  (Novell LAN WorkPlace)
        nw  =3D  NetWare       (HP 3000 servers only)
        ws  =3D  WINSOCK.DLL
        sk  =3D  WSOCKETS.DLL
        ip  =3D  W3IPC.DLL     (NetIPC, HP 3000 servers only)
 
This should work for the SCRIPTOR, but the ALLBASE ODBC driver does not=20
store information in the ODBC.INI file like most other drivers.  If you pla=
n=20
to use it with other applications, like MSQuery, there are two things you=20
may need to do:  1) Reconfigure your Network Setup on the PC so that the=20
default (possibly the *only* protocol) is the one you prefer.  I had to=20
remove IPX, but I didn't have to remove NetBEUI -- my default is WINSOCK=20
compliant.  2)  Since Data Sources aren't stored in ODBC.INI, you may have=20
to supply the Data Source information *each* time you use an Allbase Data=20
Source.  This information is kept by some applications, like MSQuery (in th=
e=20
MSQUERY.INI file), but it isn't kept by all applications.
 
If, on the other hand, you plan to develop your own apps, you should be abl=
e=20
to supply the correct parameters for each connection.
 
Carl Hughes
[log in to unmask]