Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Paradox 7 (16 bit) and IDAPI

101 views
Skip to first unread message

N. Rowe

unread,
Jan 14, 2001, 5:14:17 PM1/14/01
to
I assume that the installation of the 32 bit WordPerfect has placed
something in the registry which is controlling the pointer for the idapi
file, and that PWLocal and the switch are only working on the Win.ini file,
and not the registry. I tried removing the only reference to the Idapi file
I found in the registry, but that didn't work, and seemed kind of overkill.

Does anyone know of any other command line options I might try?


N. Rowe

unread,
Jan 14, 2001, 5:24:33 PM1/14/01
to
Sorry, part of my last message got ommitted.

We recently upgraded from Word Perfect 7 from the 16 bit to the 32 bit
version, but are still using the 16 bit version of Paradox 7. Neither
PWLocal nor the command line switch (-O) are successful in specifying an
alteranate IDAPI.CFG.

Does anyone know of any other command line options I might try to change the
IDAPI.CFG files?

(We only change the config file when the network is down. The primary config
file points to a .net file on a shared network drive, while the alternate
config file points to a local drive, and permits users access to some
locally stored tables.)


Bertil Isberg

unread,
Jan 14, 2001, 3:29:23 PM1/14/01
to
16 bits Paradox reads the name of the idapi.cfg from Win.ini [Idapi}
Section Configfile01 keyword.

[IDAPI]
DLLPATH=C:\IDAPI
CONFIGFILE01=C:\IDAPI\IDAPI.CFG

What happens when you specify the -o switch ? And what do you specify?


--
Bertil Isberg CTECH
read the newsgroup: corelsupport.faqs.paradox
for Frequently Asked Questions
---------------------------------------------------
N. Rowe <nro...@rochester.rr.com> skrev i
diskussionsgruppsmeddelandet:3a61fbe9@cnews...

N. Rowe

unread,
Jan 14, 2001, 8:04:07 PM1/14/01
to
the -o switch points to the path and filename of the alternate idapi.cfg.
I should add that both the command line and the PWLocal worked when the
machines had both 16 bit Word Perfect 7 and 16 bit Paradox 7, and still
works on machines with that setup. Loading the 32 bit Word Perfect 7
disrupted the operation.

"Bertil Isberg" <bertil...@nospam.telia.com> wrote in message
news:3a620c7d@cnews...

Bertil Isberg

unread,
Jan 15, 2001, 3:07:21 PM1/15/01
to
You still haven't said what happens when you specify the -o switch? "not
successful" is not very descriptive.

Does P7 -16 start without the -o switch? But not with the -o switch?

Where are your two versions of Bde installed?

What's the actual name of the path to the alternate idapi.cfg?

Are you using the same idpi.cfg for P7-16 and P7-32?


--
Bertil Isberg CTECH
read the newsgroup: corelsupport.faqs.paradox
for Frequently Asked Questions
---------------------------------------------------
N. Rowe <nro...@rochester.rr.com> skrev i

diskussionsgruppsmeddelandet:3a62214f@cnews...

N. Rowe

unread,
Jan 19, 2001, 12:38:31 PM1/19/01
to
Sorry I didn't get back sooner, but I was out of the office all week.

The command line for access to the tables on the Network is set as:
    C:\COREL\OFFICE\PARADOX\PDOXWIN.EXE -b -W J:\PDOX\MainData J:\PDOX\MainData\RunCase.ssl
This works fine. The  IDAPI is set in Win.ini  as C:\COREL\OFFICE\SHARED\IDAPI\IDAPI.CFG

The command line for access to the tables on the local drive is:
C:\COREL\OFFICE\PARADOX\PDOXWIN.EXE -o C:\COREL\OFFICE\SHARED\IDAPI\IDAPI-BK.CFG -w C:\LocBack C:\LocBack\Bck-Menu.ssl.

I was able to solve the problem on one machine running Windows 95, 32 bit WordPerfect and 16 bit Paradox by creating a new alternate config file with the IDAPI configuration utility. The primary config file was created with BDE configuration utility.

However on a Windows 98 machine with 32 bit Word Perfect and 16 bit Paradox,  the alternate command line gives an error finding the pdoxwin.exe file, while the command line without the switch works fine.

The win.ini sets DLLPATH=C:\COREL\OFFICE\SHARED\IDAPI.  The registry points the dll to  C:\Corel\Office7\Shared\Idapi3.

32 Bit Paradox is not being utilized at all.

Bertil Isberg

unread,
Jan 19, 2001, 3:14:09 PM1/19/01
to

a) Not related to your problem, but anyway

<<<
The command line for access to the tables on the Network is set as:
C:\COREL\OFFICE\PARADOX\PDOXWIN.EXE -b -W J:\PDOX\MainData
J:\PDOX\MainData\RunCase.ssl
>>>

When specifying the -w switch, do not use the working directory in the
spefication of the file to be opened, that is
<<<
J:\PDOX\MainData\RunCase.ssl
>>>

should be
Runcase.ssl


b)
Idapi configuration utility will only update win.ini.

Bde Configuration may update both registry and Win.ini if the Save for use
with Win3.1 and Win95/NT is checked. You'll find this setting under Object |
Options in BDE 5 Adminstrator.


c)


<<<
However on a Windows 98 machine with 32 bit Word Perfect and 16 bit Paradox,
the alternate command line gives an error finding the pdoxwin.exe file,
while the command line without the switch works fine.
The win.ini sets DLLPATH=C:\COREL\OFFICE\SHARED\IDAPI. The registry points
the dll to C:\Corel\Office7\Shared\Idapi3.
>>>

Where is 16 bits BDE stored? If you are running pdoxwin.exe, it will look in
win.ini for the DDLPATH. If the DLLPATH is incorrect, then change it to
point to the directory where the 16 bits BDE is to be found.

The Registry settings points to the 32 bits BDE, which can't be used by 16
bits Paradox.


d)


<<<
I was able to solve the problem on one machine running Windows 95, 32 bit
WordPerfect and 16 bit Paradox by creating a new alternate config file with
the IDAPI configuration utility. The primary config file was created with
BDE configuration utility.
>>>

IDAPI configuration is to be used for Paradox 5, and not for Paradox 7.
There is a BDE configuration utility for Paradox 7-16 bits and there is
another BDE Configuration utility for Paradox 7- 32bits.

There is a slight difference between Idapi and Bde. When Delphi was released
in early 1995, the Idapi was renamed to Bde. Bde cfg.exe and idapicfg.exe
are the exe files for Idapi/Bde 16 bits configuration. Bdecfg32.exe ( later
renamed to bdeadmin.exe) is for Bde 32.

--
Bertil Isberg CTECH
read the newsgroup: corelsupport.faqs.paradox
for Frequently Asked Questions
---------------------------------------------------

N. Rowe <nr...@courts.state.ny.us> skrev i
diskussionsgruppsmeddelandet:3A687B97...@courts.state.ny.us...

N. Rowe

unread,
Jan 19, 2001, 5:05:30 PM1/19/01
to
Thanks. It was the BDE's that were confusing me.

0 new messages