 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
David
Guest
|
 Posted: Fri Apr 27, 2007 2:36 pm Post subject: Component Import Problem |
 |
|
I have imported a commercial ActiveX component into BDS (using the wizard),
added it to a package and installed it, apprently successfully. The
component appears in the palette and can be placed on a form.
However, when trying to compile the application, the compiler objects to the
following statement in the generated header:
// Default Interace of OCX
_DImageViewerDisp m_OCXIntf;
and all subsequent references to _DImageViewerDisp (the component class is
TImageViewer). It appears that _DImageViewerDisp is not defined anywhere.
It would appear that the problem is all with the generated header file,
rather than the third-party software. Can anyone suggest a manual amendment
(or structure of an amendment) to the generated header file to correct this
problem please? I confess to being a straight VCL user and not having my
head around ActiveX/COM.
David |
|
| Back to top |
|
 |
Craig Farrell
Guest
|
| Posted: Fri Apr 27, 2007 11:43 pm Post subject: Re: Component Import Problem |
|
|
Hi,
| Quote: | However, when trying to compile the application, the compiler objects to the
following statement in the generated header:
// Default Interace of OCX
_DImageViewerDisp m_OCXIntf;
and all subsequent references to _DImageViewerDisp (the component class is
TImageViewer). It appears that _DImageViewerDisp is not defined anywhere.
|
The first thing I'd suggest, to try to find out more
about the design of the OCX, would be to go to File
| Open in the IDE, and change the file mask to Type
Library, and browse to and open the .OCX itself. Then
look for that type. Also, look at the "Uses" tab
where you might see other type libraries being used.
Also, check the directory where the import landed.
Do you happen to see any other .cpp files there
(that were not added to the package)? In theory,
it should all be in the headers and you should not
have to add more .cpp files.
Does the component happen to have a downloadable
eval version?
Also, can you paste here, the first couple of errors
from the message window? I am not clear if it is
compiler or linker errors that you are seeing.
--Craig |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
