I have the same problem, that other writers in this forum have, but
noone answered yet:

when linking an Active/X-Server which uses a type library from
some other vendors DLL-File I get the error

<  RLINK32: Unsupported 16bit resource in file "xyz.tlb" >

But there are no 16bit resources in the DLL, which is used
in xyz.tlb.

I hope that someone solved this problem..

Juergen Witte.

I had this problem when I tried to use a .TLB that I created in BCB 3.0.
Delphi just {*word*88}d on it. Anyway, I checked the error message and it
said something to the effect of "you should never get this message, call
Borland", so I submitted a bug report and they responded:

<---- Start Quote ---->
This reply regards BugRef 17974.

  Thank you for submitting your bug report.  It has been determined that
this is
  not a bug, but a request for technical support.  Such requests should
either be
  directed to the online forums(news://forums.borland.com) or to our
technical
  support advisor lines.
  1-888-683-2378

  Thank you.
  Anders Ohlsson,
  Delphi Developer Support

  Bug description sent:
  I get the following error:

  Error: (0): RLINK32: Unsupported 16bit resource in file
  "D:\Working\DemoOPCServer\OPCDemoServer.TLB".

<----end quote --->

Anyway, it would seem that Delphi 3.0 and C++ Builder 3.0 are not
exactly on the same par when it comes to using the entire language
construct of the Type Library definition.

In my opinion, this is either a bug, or it should be documented that
Delphi can only handle type libraries that are generated within Delphi.

Any Response Borland?

Hi Juergen,

I had the same problem with a 3rd party OCX.  The solution was to not use
the type library but always access it using late bound method calls
(oleVariant's)

This was annoying as I had referenced this type library in my own .. Some of
the return types used Interfaces from the other type library.   I had to
change all references from specific interfaces to Idispatch and drop the
reference to the other type library.
So much for the benefits of Dual Interfaces  :(

This is a real problem in Delphi .. I hope it get's fixed for version 4

I spent weeks trying to fix it ,  it only appeared in Delphi 3.1   ,  Delphi
3.0  seemed to be fine.

Peter

Hi Peter,

there was a tip in an old message in this group which only can be found
by using http://forumsearch.borland.com:88

It says to do the following:

1. Create an ServerTlb.RC File with the following content:

1 TYPELIB SERVER.TLB

2. Compile the Resource-Script into a resource file

BRC32 ServerTlb.RC

3. Instead of using {$R *.TLB} use {$R ServerTlb.RES}

This seems to work for me as workaround. I don't know
yet if there are any disadvantages..

Juergen.

Hi Aaron,

How do I know that you used a correct IDL script when compiling
it using MIDL? You didn't submit a sample script for use to try.

If you still think it's a bug, I suggest that you submit a complete
bug report with a sample so that we can reproduce the problem.

Thanks,
Anders

...

Anders,

Please accept my personal appologies for posting a Bug Report which was
incomplete. I have empathy for the difficult task made nearly impossible by
lack of information. I have resubmitted the bug report (ID# 18336) with the
offending source of the IDL file. I hope that it helps you reproduce the
problem that the several users in this thread are having.

Previously, I have only submitted bug reports when I have actually found the
problem to be in the Delphi VCL source code, and have, myself supplied a
correction as well as sample code. In this case that option was not available.

You may be perfectly correct in classifying this problem as a "request for
technical support". Bug or request for support, the desires of the
participants in this thread remain unchaged, i.e. resolution of a
compatability problem with .TLB files generated outside of Delphi 3.0.

I hope that desire may be satisfied.