BDE merge module & configuration

[Pete B]

Hi
There is not too much information to be found about BDE issues these days - I guess I should not be too surprised at that
I need to set up a BDE alias during install. The BDE MM documentation describes how to do this by including the alias configuration in a BDEmerge.ini file which must be present in the same directory as the MSI file during install. OK so I can provide that but of course an MSI file per se is only present in an uncompressed build, so I lose all the capability of compressed builds and really painfully - web based installs
I cannot find a way to make the BDEmerge.ini option work with web builds, I've tried the obvious - putting it in support files and in the same folder as all other setup files but it doesn't do the job. It looks like I'm crippling myself by using a legacy (albeit very good) technology which can't cope with IA's modern install technology.
I know that in these forums 'Tinus' and 'Orionizer' have posted on BDE issues so I am just hoping that you guys or anybody else may have a way of handling this issue. How do you set up BDE aliases during an install using a compressed or web build ?

Thanks and best wishes

Peter B

[Tinus]

Sorry Pete,

in my application I do not use an alias.

[Pete B]

Martin, thanks anyhow.

FWIW if there is anyone afflicted by this issue of not being able to use a BDEMERGE.INI file during an install using the BDE merge module, then it is possible to modify virtually any aspect of BDE configuration programmatically from within your application. This was the way I had to go and it works well, getting the app. to configure the BDE as required. Borland provide a very good resource for using the BDE API from this link :

http://info.borland.com/devsupport/bde/bdeapiex/

If you get stuck with the BDE merge module, I hope it helps you as much as it did me.

Pete B.