>>But all the binaries for the main server and all the utilities retain theJust trying to do some informal risk management for the following scenario.
>True - I think this renaming the client library, server filename, default
>port etc is scheduled for version 2.
I am planning to use FB as an embedded database.
My installation program will have an option "install server" and basically FB server will be installed
My "install client" option will install the FB client dll and my delphi exe.
Suppossing some other application does something similar and installs IB6.5,
I am certain to have mysterious problems at that customers site.
As of now I am talking of the Windows server.
(I have never worked on Linux. I have started
Prompted by all the traffic on this list of how much better it is to run FB on Linux)
What can be done to minimize this risk.
will something like this work.
rename gds32.dll to fbs32.dll
Have a seperate shipment version of IBO bound into my exe
where a search and replace is done to replace all occurences of gds32.dll with fbs32.dll
Rename ibserver.exe to fbserver.exe.
Rename ibguard.exe to fbguard.exe (probably cause a problem)
Q. How can i tell ibguard that ibserver has been renamed.
Q. Can I create some configuration file so that fbserver.exe will listen on a different port.
Q. What do I need to do in IBO to tell it to use the new port.
< I am cross posting this on the IBO and IB lists because the question spans some boundaries >
Any thoughts and ideas welcome