Thanks very much for the suggestion...
Am still pondering though,,,,
On one workstation, it does have a path to orawin95\bin, but still can not
connect to the database.
On a 2nd workstation, the path exists, but the regestry keys do not exist,
but it works...?
Could you be suggesting by your statement (above) that we need to make a
key entry for our program in the registry, as to where to locate all DLL's
for this app.?
Could you expound a little more on your suggestion?
In the meantime, we're going to remove Infomaker, PB & Oracle software and
regestry keys and reinstall Powerbuilder and Oracle on the 1st example
Thanks much for your ideas
From: "Dave C." <DCarnahan@GW.ODH.STATE.OH.US>
Subject: Infomaker 6.5 Deploying. - Hitting Oracle back-end... REPLY:
X-Newsreader: Microsoft Internet News 4.70.1155
Date: Tue, 06 Jul 1999 10:30:21 -0400
Xref: forums-1-dub sybase.public.infomaker.general:6130
Article PK: 240069
From: "Terry Dykstra" <firstname.lastname@example.org>
Subject: Re: Infomaker 6.5 Deploying. - Hitting Oracle back-end... REPLY:
Date: Tue, 6 Jul 1999 08:49:51 -0600
X-Newsreader: Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700
Xref: forums-1-dub sybase.public.infomaker.general:6128
Article PK: 240064
If the deployment dlls (like pbvm60.dll etc) are in the same directory as
the exe, you don't need an entry in the app path, as long as the
orawin95\bin directory is in the path. If either are not in the path, you
need the app path entry. Personally I try to keep things as simple as
possible, by having orawin95\bin in my path in autoexec.bat and putting my
exes on the network in one directory, together with the deployment dlls.
You must have an entry for sqlnet in the registry. It is in the following
I run my sqlnet from the network. That way I don't need to install it on
any PC, other than putting in the registry entry and the path statement.
Terry Dykstra (TeamSybase)
Canadian Forest Oil Ltd.