At 06:15 PM 19/01/2007, mitch_landor wrote:

> > >Any other suggestions?
> >
> > Can't think of any without more info about what the app is doing at
>startup.
>
>I did not compile using runtime libraries.
>
>Here is my main form code. There is a splashscreen which was also in
>my version 1 demo. Just to be sure I tested it while disabled and
>still get the problem.

I guess I should have said "info about what kind of data access stuff
the app is doing at startup". This list isn't for general Delphi support...

That said, I don't see any "escape routes" there for all those modal
forms in those procedure implementations (possibly hidden in
TFormContainer, which looks like some kind of third-party
class); and I'm also inclined to wonder whether you remembered to
comment out all of the Create calls for these forms in your
DPR. Worth looking; though hangups due to crises in form management
are a Delphi issue, not an IBO one.

(Assuming you're using Billennium for gee-whiz visual effects, are
you even certain that the platforms you have deployed to actually
support that stuff? Might be an issue if you haven't visited it before...)

That apart, there's nothing visible in the main form's code that has
anything to do with data access at all. If you killed the
splashscreen, what's supposed to happen next? Does it work? Then
next...does it work? and so on.

At some point presumably you are going to try to connect to a
database...and you say it is happening on your local setup. Given
the changeover from Fb 1.5 to Fb 2.0, have you overlooked any of the
prep work required after the upgrade? (Read the Compatibility and
Security sections in the Fb 2 releasenotes.)

Are you sure all your clients are using the right client library,
including finding it in the right place? There is a known issue with
using Interbase client to access Fb 2.0, that is fixed in the
upcoming v.2.0.1, though I understand this exhibits as server crashes
rather than client hangups.

And, given that you mentioned you changed the database name in the
deployment version, you should probably check around your
TIBODatabase Params and DatabasePath to see whether you've overlooked
a hard path hanging around somewhere.

I'd also rename my development copy of the DB to the same name as
that on the deployed server and test whether things are still as
sweet as you thought WRT path access. That would help for knowing
whether the Fb 2 upgrade is causing the problems, or just leftover
artifacts/dependencies from your older versions. Also check
firebird.conf on the deployed servers and make sure the Fb 2
configuration defaults fit with what you're doing over there.

Finally, as the last scraping of the bucket from my POV, I again
remind you that IBO 4.6B does not fully support Fb 2.0. If it turns
out that the problem comes from something tripping up on an
unsupported Fb 2.0 feature or behaviour, there's nothing to do but
wait for the 4.7 release.

Helen