| T O P I C R E V I E W |
| znakeeye |
Posted - Apr 27 2008 : 07:31:36 AM
ActiveX components often come with a TLB file. You include it like this:
#import "ActiveXComponent.tlb"
This generates a TLI and a TLH file. The TLH has all the definitions that are needed for VAX to successfully parse the document. However, VAX is not aware of this!
From MSDN:
Both header files are placed in the output directory specified by the /Fo (name object file) option. They are then read and compiled by the compiler as if the primary header file was named by a #include directive.
Due to this, VAX is rendered useless when working with TLBs. I hope you can fix this any time soon! |
| 4 L A T E S T R E P L I E S (Newest First) |
| znakeeye |
Posted - May 05 2008 : 08:14:40 AM
That's a solution. Thanks. |
| feline |
Posted - Apr 30 2008 : 12:31:07 PM
Personally I do not know anything about working with TLB or TLH files. I am familiar with them from bug reports, but that is it.
Have you considered adding a #include statement, but wrapping it in #if 0, #endif ?
This way VA will still see the #include line, but the compiler will ignore it. |
| znakeeye |
Posted - Apr 29 2008 : 3:44:06 PM
TLB = 269 kB
TLH = 774 kB
TLI = 745 kB
The problem I'm seeing is that since I do not explicitly include the tlh-file (which you should not), it is not being parsed. Simple as that.
I just opened a project linked with a specific TLB, and it compiled. Tried to edit it, and none of the symbols were recognized by VAX until I explicitly included the tlh-file with an #include-statement (of course I had to remove it afterwards, to avoid multiple declarations). A BUG! *hunts* |
| feline |
Posted - Apr 28 2008 : 5:48:59 PM
What problems are you seeing?
*hunts* yes, there is a bug report about VA having a problem with an Excel TLH file that is 5meg in size. The problem here is that this specific TLH file is to large.
VA does support TLH files, and this does work, assuming the files are not to large. How large are the TLH files you are working with? |
