Peter,
Any initialisation can cause exceptions, many Tstringlists etc are
created in various places. Also formcreates can cause exceptions.
In our case, the saga started with exceptions in the formcreate of
the datamodule (containing the tdatabase component for thr project).
This needs to be created before any database access in any other
forms. Bracketing the bulk of the dpr code with try-except
prevented the rest of the forms from being created and prevented the
app from running, as required.
The app fails nicely when the database/path is invalid, with a good
descriptive exception message. Thats spoilt by VCL generated
exceptions that follow the above. Mostly 2 of them, sometimes 3.
Yes, I know, yet another thing to track down in the VCL and fix. :-)
On 7 May 99 at 12:08, [EMAIL PROTECTED] wrote:
> What exceptions are you getting at initialisation that you need to trap in the
> project file? Why can't they be trapped in the unit files?
Rohit
======================================================================
CFL - Computer Fanatics Ltd. 21 Barry's Point Road, AKL, New Zealand
PH (649) 489-2280
FX (649) 489-2290
email [EMAIL PROTECTED] or [EMAIL PROTECTED]
======================================================================
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
