The only reason you should have problems like this with included units is if
you are using classes that are in the units. In this case, TApplication
class, which I thought was actually part of an application anyway.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
On a slightly different track ...
I don't know exactly what you are doing, but in D6 the need for the forms
unit etc is greatly reduced. This is thankfully due to Kylix - ie anything
visual, is no longer required in Units like DB etc.
All you need is a message prcoessing loop.
Myles.
-Original Message-
From: Patrick Dunford [EMAIL PROTECTED]
To: Multiple recipients of list delphi [EMAIL PROTECTED]
Date: Wed, 22 Aug 2001 10:16:51 +1200
Subject: RE: [DUG]: Application.processmessages
The only reason you should have problems like this with included units
is if
you are using
Type in application.processmessages.
Ctrl-Click on it.
See the code.
Copy and paste.
Get rid of anything which is not Win APIs.
Alex
- Original Message -
From: vss [EMAIL PROTECTED]
To: Multiple recipients of list delphi [EMAIL PROTECTED]
Sent: Wednesday, August 22, 2001 7:57 AM
Dear Patrick,
If your Delphi version is Delphi 5, check Delphi 5\bin directory, there
should exist a file called tlibimp.sym. In section Winword, you will see
line
Application=WordApplication
That is how Borland avoid foreign coclass name conflict with Delphi reserve
word and internal VCL
I imported the Word 8 Type Library into my project as Word_TLB. However
the
compiler now refuses to compile Application.ProcessMessages, giving the
compiler error "Object or class type required". Any ideas how to fix this
problem?
Use Forms.Application.ProcessMessages. And include Forms in
