PDA

View Full Version : Installshield Exp Delphi Edition - Doesn't configure the NEW MSACCESS Driver Properly



NewsArchive
12-20-1997, 01:00 AM
Can anyone help,

I have a Delphi 3.0 (actually 3.02 C/S) application, which requires the NEW
(D3.01+) native MSACCESS driver. However, the Installshield D3 Edition
FULL BDE install seems to be configuring the native MSACCESS driver as if
it was the previous version. If I go into BDE admin on the clients PC, it
shows the native MSACCESS driver, which does not have a place to specify
the system database (Nor does it create it if I specify SYSTEM
DATABASE=somepath\system.mdw). If I install the BDE directly from the
D3.01 CD (not using Installshield), then the Installshield setup configures
the NEW driver properly (ie the driver has a SYSTEM DATABASE parameter),
and the application works. However, I can't go to each user's desktop and
install BDE from the CD. The installation program was created on a machine
that DOES have the new Native MSACCESS driver.

Gregg

--
An extra "x" has been inserted into my e-mail address to reduce spam.
To e-mail me directly, remove the "x".

NewsArchive
12-20-1997, 01:00 AM
On 20 Dec 97 04:48:18 GMT, "Gregg" <beaseyg@xkodinet.com> wrote:
>DATABASE=somepath\system.mdw). If I install the BDE directly from the
>D3.01 CD (not using Installshield), then the Installshield setup configures

What I suggest is that you update your BDE from the CD, and then update
Express (by either uninstalling and reinstalling it, or by unchecking the
BDE option, rechecking it, configuring your aliases and then rebuilding
your installation.


Stefan
ellipse data systems

NewsArchive
12-24-1997, 01:00 AM
Stefan,

Re-installing didn't work, I even tried installing Installshield Express 2
but that didn't work either. I did manage to figure out how to resolve the
problem though. (Note that my problem had nothing to do with IDDA3532.DLL
problem that others reported). It turns out that the IDAPI32.CNF file that
is packaged in the Installshield redist directory is apparently an older
version (which didn't support the SYSTEM DATABASE parameter for the Native
MSACCESS Driver). To resolve it, I ran BDEADMIN and deleted out all the
Aliases out of my existing IDAPI32.CFG (in the Borlands BDE directory) and
saved the file as IDAPI32.CNF (thus my original IDAPI32.CFG was never
altered). Then I copied the IDAPI32.CNF file to the REDIST directory and
recreated my installation files. Lo and behold everything installs
perfectly on the other PC's..

Gregg

PS. This message was originally posted on
Borland.Public.Delphi.Database.Desktop, but I thought it might be of
interest to the Installshield people as well, as this may be something they
want to adjust in a maintenance release, since it effects Installshield
Express 2 as well.

Stefan Paetow <owner@ellipse-data.com> wrote in article
<349bf9dd.20072632@news.installshield.com>...
> On 20 Dec 97 04:48:18 GMT, "Gregg" <beaseyg@xkodinet.com> wrote:
> >DATABASE=somepath\system.mdw). If I install the BDE directly from the
> >D3.01 CD (not using Installshield), then the Installshield setup
configures
>
> What I suggest is that you update your BDE from the CD, and then update
> Express (by either uninstalling and reinstalling it, or by unchecking the
> BDE option, rechecking it, configuring your aliases and then rebuilding
> your installation.
>
>
> Stefan
> ellipse data systems
>

NewsArchive
12-24-1997, 01:00 AM
Stefan,

Re-installing didn't work, I even tried installing Installshield Express 2
but that didn't work either. I did manage to figure out how to resolve the
problem though. (Note that my problem had nothing to do with IDDA3532.DLL
problem that others reported). It turns out that the IDAPI32.CNF file that
is packaged in the Installshield redist directory is apparently an older
version (which didn't support the SYSTEM DATABASE parameter for the Native
MSACCESS Driver). To resolve it, I ran BDEADMIN and deleted out all the
Aliases out of my existing IDAPI32.CFG (in the Borlands BDE directory) and
saved the file as IDAPI32.CNF (thus my original IDAPI32.CFG was never
altered). Then I copied the IDAPI32.CNF file to the REDIST directory and
recreated my installation files. Lo and behold everything installs
perfectly on the other PC's..

Gregg

PS. This message was originally posted on
Borland.Public.Delphi.Database.Desktop, but I thought it might be of
interest to the Installshield people as well, as this may be something they
want to adjust in a maintenance release, since it effects Installshield
Express 2 as well.

Stefan Paetow <owner@ellipse-data.com> wrote in article
<349bf9dd.20072632@news.installshield.com>...
> On 20 Dec 97 04:48:18 GMT, "Gregg" <beaseyg@xkodinet.com> wrote:
> >DATABASE=somepath\system.mdw). If I install the BDE directly from the
> >D3.01 CD (not using Installshield), then the Installshield setup
configures
>
> What I suggest is that you update your BDE from the CD, and then update
> Express (by either uninstalling and reinstalling it, or by unchecking the
> BDE option, rechecking it, configuring your aliases and then rebuilding
> your installation.
>
>
> Stefan
> ellipse data systems
>