Board index » off-topic » BDE Installation

2003-12-03 06:11:46 AM
off-topic0
Whenever some customers of mine try to install an application created with
Delphi 5 and they already have an older version created with Delphi 3, the
BDE refuses to merge the IDAPI.CFG file and the new application will not
run.
This happens in every case when the Delphi 3 version of BDE is already
installed on the machine. For some reason the merge file name reported by
Installshield is not IDAPI32.CFG but IDAPI.CFG.
I have read all the stories on Borland website but is there a simple way of
reinstalling the BDE?
I am not comfortable with customers deleting things from registry as they
are mostly computer illiterate people.
Thanks, John
 

Thanks for the suggestion. However, I wonder if there is anything I can do
to avoid the problem in the first place. As it stands now, every customer
who has a Delphi 3 version of BDE installed cannot install BDE enabled apps.
created with D5 because the merge bombs and the new BDE will not install. It
is not a user-friendly option to ask customers to download and install the
BDE from somebody else's website. Many of them are not even connected to
Internet.
Is there anything I can do to avoid the problem? Certainly, I am not the
only one who encounters it .
Thanks, John
"Bill Todd" < XXXX@XXXXX.COM >wrote in message

John wrote:
Steve Green - Diamond Software Group, Inc - Waldorf Maryland USA
Corel CTech Paradox - www.diamondsg.com - Support/Sales/Links
---------------------------------------------------------------------------
Our latest web site update is in place - new Support and Sales options!
---------------------------------------------------------------------------
 

{smallsort}

1.) I use Installshield that came with Delphi 5
2.) Error Message: Merging the configuration file has failed Config File:
c:\program files\common files\borland\shared\dbe\idapi.cfg
This is not a single occurrence, this seems to happen on nearly all machines
that have D3 ver. of BDE installed.
I wonder if it has something to do with InstallShield using idapi.cfg.
Should it not be idapi32.cfg?
"Bill Todd" < XXXX@XXXXX.COM >wrote in message

I could say something but I just ignore smart-arses who nit-pick instead
trying to help.
"Steven Green" < XXXX@XXXXX.COM >wrote in message

I could be wrong here (I don't use InstallShield anymore), but I think
there's an option about whether or not the config will support 16 and/or 32
bit versions of the BDE. I expect idapi.cfg is the 16/32 bit version while
idapi32.cfg is for the 32-bit only version. The D3 installs probably have
16/32 bit config files that you're trying to merge with a 32-bit only
version from your install. Maybe if you change the config file your
distributing to support 16/32 bit the merge will work?
"John" < XXXX@XXXXX.COM >wrote in message

Yes, you might be right there. I have installed the D5 app.on the hard disk
which I use for D3 compatibility and it installed OK & the config file was
idapi32.cfg while on the my D5 HD it uses idapi.cfg config file.
There might be some interaction from D1 or Paradox 5 16 bit IDAPI stuff.
The problem is to figure what happens on the customers computer without
having access to it. I found that you can fresh install BDE if you rename
(or delete) the BLW32 & Database Engine entries in registry and rename
(delete) the BDE folder on the HD. Interestingly, InstallShield still
locates the config file. I guess it finds it in win.ini file IDAPI entry.
"C P" < XXXX@XXXXX.COM >wrote in message

John wrote:
*you* download it once, then deploy it with your stuff.. upgrade the BDE, then
install the app.. geez <g>
Steve Green - Diamond Software Group, Inc - Waldorf Maryland USA
Corel CTech Paradox - www.diamondsg.com - Support/Sales/Links
---------------------------------------------------------------------------
Our latest web site update is in place - new Support and Sales options!
---------------------------------------------------------------------------
 

on the machine. But we use Wise.
--
Gert
 

God you are clever, wonder what would we do without your advice.
"Steven Green" < XXXX@XXXXX.COM >wrote in message

John wrote:
and looking foolish..
the people here, myself included, donate an unbelievable amount of time, just to
help those with problems.. like you.. you won't endear yourself to the community
with your continued rude comments..
Steve Green - Diamond Software Group, Inc - Waldorf Maryland USA
Corel CTech Paradox - www.diamondsg.com - Support/Sales/Links
---------------------------------------------------------------------------
Our latest web site update is in place - new Support and Sales options!
---------------------------------------------------------------------------
 

Sorry if I offended someone. I did not know Steve is part of your team as
his name does not appear on any other messages, I thought he just jumped in.
My apology...
The point is that I know how to download and send files to new customers.
I am here concerned how to fix a problem on an existing customer
installation. I was trying to find a solution I could resolve with the
customer over the phone rather than sending him programs to run.
Thanks for all your help.
Regards
John
"Bill Todd" < XXXX@XXXXX.COM >wrote in message

John wrote:
their responses to be meaningful.. when the answer is wrong, then the "team"
will point that out.. to great excess <g>
Steve Green - Diamond Software Group, Inc - Waldorf Maryland USA
Corel CTech Paradox - www.diamondsg.com - Support/Sales/Links
---------------------------------------------------------------------------
Our latest web site update is in place - new Support and Sales options!
---------------------------------------------------------------------------
 

Help Please. I've used BC++ version 5 for years to develop applications.
These applications were either run from the machine where they were
developed, or moved to machines that had previous installations of BDE.
Recenty, for the first time, I created an installation CD with Install
Shield Express 1.0 and sent it to someone with a "clean" machine - no
previous Borland products. The installation went flawlessly (Windows 98)
but the application fails to initialize the BDE - throwing the error
"Invalid File Name" during initialization. Then, of course, everywhere you
try to open a file in the application you get that error again. I've
checked both my development machine and the target machine for dlls, exes,
cfg files, etc. Everything is the same on both machines. Registry entries
related to idapi and bde are the same on both machines.
Any ideas?
Rob Graham
 

"Bill Todd (TeamB)" < XXXX@XXXXX.COM >wrote:
"Invalid File Name"
Rob