Subject | Re: [IBO] Desperate...IBO 4.6b - DB Connection error after upgrade to FB2 |
---|---|
Author | mitch_landor |
Post date | 2007-01-18T08:09:38Z |
I have done a complete search of the system and now the only
fbclient.dll is in the c:\Program Files\Firebird\Firebird_2_0\bin
directory. But I still have the problem.
--- In IBObjects@yahoogroups.com, "Roger Vellacott" <rvellacott@...>
wrote:
fbclient.dll is in the c:\Program Files\Firebird\Firebird_2_0\bin
directory. But I still have the problem.
--- In IBObjects@yahoogroups.com, "Roger Vellacott" <rvellacott@...>
wrote:
>
> Make sure there are no old versions of fbclient.dll in the
> Windows\System32 folder, and elsewhere.
>
>
> Roger Vellacott
> Passfield Data Systems Ltd
>
>
>
> -----Original Message-----
> From: mitch_landor [mailto:mlq97@...]
> Sent: 18 January 2007 07:34
> To: IBObjects@yahoogroups.com
> Subject: [IBO] Desperate...IBO 4.6b - DB Connection error after upgrade
> to FB2
>
>
>
> I am developing a Delphi/Firebird app using only TIBO components.
>
> I started with FB1.5 and successfully deployed a demo version of my
> app to my client's pc, using FB1.5. I then upgraded to Firebird 2.0 on
> my development machine and continued development.
>
> I now wish to deploy the latest version of my software to my client's
> pc. So on their machine I uninstalled FB1.5 and installed FB2.0. I
> then installed my app but I can't get it to work. The splash screen
> comes up and then it hangs with the windows error "XXX.exe has
> encountered a problem and needs to close."
>
> I can't make any sense of the detailed error message. I thought
> perhaps the FB2.0 database was not working, so I installed IBExpert
> and I can connect OK. The DB seems fine.
>
> I have used SYSDBA & masterkey throughout.
>
> The hosts file is unchanged and showing localhost.
> The FB alias file seems to be correct. I did change the DB file name
> in this from DB00.fdb (1st demo) to DB01.fdb (second demo) but
> otherwise the path is the same.
>
> Please does anyone have any suggestions for what I could check that
> might be causing the problem? It all runs OK on my development machine.
>
> Thanks
>
> Mitch
>