Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Infomaker 6.5 Deploying.- Hitting Oracle back-end....

2 posts in PB Infomaker Report Writer Last posting was on 1999-07-02 21:18:51.0Z
Dave C. Posted on 1999-07-01 17:18:42.0Z
Newsgroups: sybase.public.infomaker.general
From: "Dave C." <DCarnahan@GW.ODH.STATE.OH.US>
Subject: Infomaker 6.5 Deploying.- Hitting Oracle back-end....
X-Newsreader: Microsoft Internet News 4.70.1155
Date: Thu, 01 Jul 1999 13:18:42 -0400
Lines: 28
Message-ID: <348_01bec3e5$e759c620$9d88eac6@USER.gosip.ohio.gov>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6136
Article PK: 240070

Sybase support,


We're having a significant problem deploying a working Infomaker 6.5
'stand-alone' or
not 'stand-alone' program connecting to an Oracle 7.3 database located on a
Windows NT box.

We're on a Novell 4.11 OS network...using Windows 95 OSR 2.b on our
workstations.

We have made an executable image called 'Daily.exe' and copied 3 other
files from your
recommended deployment / dddk6 install program and deposited them upon a
sub-directory
called C:\FRS

[1] PBVM60.DLL
[2] PBOR7360.DLL
[3] PBDEW60.DLL
[4] DAILY.EXE
[5] DAILY.INI

Nothing else is in this sub-directory.

Now -

Our error (upon invoking DAILY.EXE) say's 'Can not connect to database',
but we can connect to the database - if we use Oracle's 'Net8 Easy Config'
testing program to
'ping' the Oracle listener.

Given these facts (above) and assuming that they are correct (?)
Can you please confirm this set of deployment instructions is on solid
ground, if not,
Where should we be looking to detect a fault in our logic as to our method
of building a program.


Terry Dykstra Posted on 1999-07-02 21:18:51.0Z
Newsgroups: sybase.public.infomaker.general
From: "Terry Dykstra" <tdykstra@cfol.ab.ca>
Subject: Re: Infomaker 6.5 Deploying.- Hitting Oracle back-end....
Date: Fri, 2 Jul 1999 15:18:51 -0600
Lines: 50
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_XmjnhANx#GA.205@forums.sybase.com>
References: <348_01bec3e5$e759c620$9d88eac6@USER.gosip.ohio.gov>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6133
Article PK: 240067

You need to add orawin95\bin to your path in autoexec.bat, or else in the
app path in the registry. As an example, take a look at the entry for
im60.exe in the registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App
Paths\im60.exe]

--
Terry Dykstra (TeamSybase)
Canadian Forest Oil Ltd.

Dave C. wrote in message <01bec3e5$e759c620$9d88eac6@USER.gosip.ohio.gov>...
>Sybase support,
>
>
>We're having a significant problem deploying a working Infomaker 6.5
>'stand-alone' or
>not 'stand-alone' program connecting to an Oracle 7.3 database located on a
>Windows NT box.
>
>We're on a Novell 4.11 OS network...using Windows 95 OSR 2.b on our
>workstations.
>
>We have made an executable image called 'Daily.exe' and copied 3 other
>files from your
>recommended deployment / dddk6 install program and deposited them upon a
>sub-directory
>called C:\FRS
>
>[1] PBVM60.DLL
>[2] PBOR7360.DLL
>[3] PBDEW60.DLL
>[4] DAILY.EXE
>[5] DAILY.INI
>
>Nothing else is in this sub-directory.
>
>Now -
>
>Our error (upon invoking DAILY.EXE) say's 'Can not connect to database',
>but we can connect to the database - if we use Oracle's 'Net8 Easy Config'
>testing program to
>'ping' the Oracle listener.
>
>Given these facts (above) and assuming that they are correct (?)
>Can you please confirm this set of deployment instructions is on solid
>ground, if not,
>Where should we be looking to detect a fault in our logic as to our method
>of building a program.
>