I have a D7 project that I have upgraded to D2007. When I run it, it gives
the following error:
---
Application Error
---
Exception EReadError in module PPrint4.exe at 00460737.
Error reading frmBase.TextHeight: Property TextHeight does not exist.
Could be something to do with your uses clause. Whatever class is
supposed to have these properties may be declared twice (different
version, or completely different classes with the same name) in
different units, and in this case it is using the wrong one and
therefore stuffing up.
Stacey
The class's descend from TForm, and they are TForm properties.
Regards
Sean Cross
IT Systems Development Manager
Catalyst Risk Management
PO Box 230
50 Dalton St
Napier 4140
DDI: 06-8340362
mobile: 021 270 3466
Visit us at http://www.catalystrisk.co.nz/
Offices in Auckland, Napier, Wellington
This happened to me when I had Quick Report without
the form.
Create new Form, select all in old form and paste on
new form. Change calls.
--- Sean Cross [EMAIL PROTECTED] wrote:
I have a D7 project that I have upgraded to D2007.
When I run it, it gives
the following error:
I will give that a try. However I am getting the error showing up on an empty
form with no changes.
Regards
Sean Cross
IT Systems Development Manager
Catalyst Risk Management
PO Box 230
50 Dalton St
Napier 4140
DDI: 06-8340362
mobile: 021 270 3466
Visit us at http://www.catalystrisk.co.nz/
Has anyone managed to use mdi forms in a unit test? I keep getting the error
Cannot create form. NO MDI forms are currently active.
I have tried creating and showing an mdi form first without any luck. I have
also tried creating an inherited child form with a formstyle of fsnormal but
that
Did you create a parent MDI form first?
On Mon, 21 May 2007 11:47, Sean Cross wrote:
Has anyone managed to use mdi forms in a unit test? I keep getting the
error Cannot create form. NO MDI forms are currently active.
I have tried creating and showing an mdi form first without any luck. I
Yes. I am doing this
procedure TestTfrmOrders.SetUp;
begin
...
FmdiParent:= TformMdiParent.Create(Application);
FmdiParent.Show;
Application.ProcessMessages;
FfrmOrders := TfrmOrders.Create(Application);
end;
Regards
Sean Cross
IT Systems Development Manager
Catalyst Risk
Interesting. It appears (in D2006 anyway) MDI forms are only supported if
the *main form* of the application is an MDI parent form:
procedure TCustomForm.CreateWindowHandle(const Params: TCreateParams);
var
CreateStruct: TMDICreateStruct;
NewParams: TCreateParams;
begin
if (FormStyle =
