| Subject | Re: [IBO] Stand alone Server DLL |
|---|---|
| Author | Helen Borrie |
| Post date | 2008-01-04T02:31:39Z |
At 11:36 AM 4/01/2008, you wrote:
If the application sends the correct protocol and path, the client library itself knows what to connect to. So - assuming you plan to deploy your application with fbembed.dll (renamed to fbclient.dll, of course), for use as a single, stand-lone, embedded-server application - please RE-READ my earlier posting.
In the IDE, you should not use the (renamed) fbembed.dll as your client library. This is because (usually) the Delphi IDE makes a connection to your database using the found client library. Because the Delphi IDE and your application run in the application spaces of different Windows users, the application will not be able to access the database because the user localsystem has an exclusive shared lock on the database file.
Instead, develop under the full Superserver (not Classic) and use cpLocal for your protocol. In testing and for deployment - provided you have set up your application structure properly as described in the Firebird release notes - your exe will run correctly with the properly located fbembed.dll (renamed to fbclient.dll).
Helen
>Thanks for the reply..The application NEVER calls the firebird server. The application loads the client library, which is named fbclient.dll, or renamed to gds32.dll. The application itself doesn't know what model of server it is connecting to, because it doesn't need to know.
>
>Dont I have to list the Embedded dll somewhere or will it automaticly know to call the DLL instead of the firebird server?
If the application sends the correct protocol and path, the client library itself knows what to connect to. So - assuming you plan to deploy your application with fbembed.dll (renamed to fbclient.dll, of course), for use as a single, stand-lone, embedded-server application - please RE-READ my earlier posting.
In the IDE, you should not use the (renamed) fbembed.dll as your client library. This is because (usually) the Delphi IDE makes a connection to your database using the found client library. Because the Delphi IDE and your application run in the application spaces of different Windows users, the application will not be able to access the database because the user localsystem has an exclusive shared lock on the database file.
Instead, develop under the full Superserver (not Classic) and use cpLocal for your protocol. In testing and for deployment - provided you have set up your application structure properly as described in the Firebird release notes - your exe will run correctly with the properly located fbembed.dll (renamed to fbclient.dll).
Helen