BDE Admin - Use as a custom action
Good Morning
Hope someone can help. I have been handed a msi package from an external source which has some custom actions which attempts to configure BDE. On testing the app with Installshiled Admin I receive the error 'Unable to Merge New Configuration, Use BDE Administrator to Merge'. The package does install, but the file idapi32.cfg does not copy over correctly, instead a copy of the file sized 81 bytes is present, not the correct size of 6080 bytes as should be. On launching the app the error 'System Alias "Alias Name" does not exist in your default database configuration'. This is resolved by manually replacing the file idapi32.cfg with the correct one, the app then works.
I am fairly new to packaging especially dealing with custom actions - if anyone has a fairly simple workaround it would be greatly appreciated.
Hope someone can help. I have been handed a msi package from an external source which has some custom actions which attempts to configure BDE. On testing the app with Installshiled Admin I receive the error 'Unable to Merge New Configuration, Use BDE Administrator to Merge'. The package does install, but the file idapi32.cfg does not copy over correctly, instead a copy of the file sized 81 bytes is present, not the correct size of 6080 bytes as should be. On launching the app the error 'System Alias "Alias Name" does not exist in your default database configuration'. This is resolved by manually replacing the file idapi32.cfg with the correct one, the app then works.
I am fairly new to packaging especially dealing with custom actions - if anyone has a fairly simple workaround it would be greatly appreciated.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
cdupuis
20 years ago
Try using the Merge Module instead.
http://info.borland.com/devsupport/bde/bdeupdate.html
http://info.borland.com/devsupport/bde/bdeupdate.html
Posted by:
MSIram
20 years ago
Write a VBScript or a command file which will copy the required idapi32.cfg file every time you launch the shortcut.
here is a wage logic..
the script should contain :-
1) copy idapi32.cfg file ( the original one from some location) to c:\progra~1\common files\bde\.. location.
2) launch the application exe file.
Now make this script as your shortcut... which will solves your problem
This is just like manually coping the file to the required location and then launching the shortuct... hope this helps..
here is a wage logic..
the script should contain :-
1) copy idapi32.cfg file ( the original one from some location) to c:\progra~1\common files\bde\.. location.
2) launch the application exe file.
Now make this script as your shortcut... which will solves your problem
This is just like manually coping the file to the required location and then launching the shortuct... hope this helps..
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
