🚀 go-pugleaf

Try to place your BCB dll somewhere into PATH, for example in
C:\Windows\System in Win9x or C:\Windows\System32 in WinNT, Win2000, WinXP.

If you create sample dll with one exported simple function, could they load
with with VB?

BTW, error 430 is described in MSDN like: "Class does not support Automation
or does not support expected interface." Could problem be in VB?

Here is Q193172 from MSDN, other sources also say "Class does not support
Automation or does not support expected interface.":

SYMPTOMS
When the project type of an ActiveX server is changed from DLL to EXE and
recompiled, any client code that attempts to create an instance of an object
from the server generates the following error:

"Run-time error '430' : Class does not support Automation or does not
support expected interface."
CAUSE
The error results from project compatibility and the change of the project
type from DLL to EXE. In project compatibility, Visual Basic preserves the
Class ID (CLSID) of the class but not the Interface ID (IID). Because the
CLSID is preserved, the class ends up being registered with two servers; the
in-proc server (DLL) and the local server (EXE). As you create an instance
of the class from a client, the class from the DLL is chosen. Because the
class from the DLL does not support the new IID, the above error occurs.
RESOLUTION
Use the RegSvr32.EXE utility to unregister the old DLL server and re-
register the new EXE server to eliminate this error.
STATUS
Microsoft is researching this problem and will post new information here in
the Microsoft Knowledge Base as it becomes available.

//------------------------------------------
Regards,
Vassiliev V. V.
http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
ADO.Net
http://www.oledbdirect.com - The fastest way to access MS SQL Server,
MS Jet (Access) and Interbase (through OLEDB)

"YangKai Liu" <yangkai.liu@burkelee.com> �������/�������� � ��������
���������: news:414a9d29@newsgroups.borland.com...
> Yes, they want to create additional ActiveX DLL with VB that calls my DLL.
> The message is a run-time error message.  As you may already know, the
> debugging environment messages from VB regarding linking DLL are quite
> unstable and sometines false.  The debugging environment message is
> something like "unable to locate DLL".
>
> I know the better is to create the Active X DLL directly from BCB6, but
for
> some non-technical reason, it is not feasible.
>
> Thanks for helping me.
>
> Best Regards,
>
>
> YangKai Liu
>
> "Viatcheslav V. Vassiliev" <support@oledbdirect.com> �b�l��
> news:41497796@newsgroups.borland.com �����g...
> > It is better to have newer MDAC.
> >
> > > repackage it into ActiveX DLL using Visual Basic 6
> > I do not understand what they want to do. Create additional VB dll that
> uses
> > your Delphi DLL? When they get this message - when compiling VB dll?
> >
> > And why not write this ActiveX dll in Delphi - you will have one dll
that
> > does not depend on msvbvm60.dll?
> >
> > //------------------------------------------
> > Regards,
> > Vassiliev V. V.
> > http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
> > ADO.Net
> > http://www.oledbdirect.com - The fastest way to access MS SQL Server,
> > MS Jet (Access) and Interbase (through OLEDB)
> >
> > "YangKai Liu" <yangkai.liu@burkelee.com> ������?�������� ?��������
> > ��������? news:41492eb3@newsgroups.borland.com...
> > > The problem I encountered is as follows:
> > > I made a DLL which accesses databases with ADO.  The IT at the
> production
> > > site tries to repackage it into ActiveX DLL using Visual Basic 6.
> > > Then we have error message 430, which, according to Microsoft, is
caused
> > by
> > > "the application references one version of ADO and redistributes a
> > different
> > > version of ADO."
> > >
> > > Can I tell the IT at the production site to use an older version of
ADO
> to
> > > fix the problem?
> > >
> > >
> > > "Viatcheslav V. Vassiliev" <support@oledbdirect.com> �b�l��
> > > news:41492cf6$1@newsgroups.borland.com �����g...
> > > > This depends on which features your program uses. Usually MDAC 2.5
is
> > > > enough. But, of course, newer version is better. SP4 has no changes
in
> > > > MDAC - you could download MDAC from Microsoft site.
> > > >
> > > > //------------------------------------------
> > > > Regards,
> > > > Vassiliev V. V.
> > > > http://www.managed-vcl.com - using .Net objects in Delphi for Win32
+
> > > > ADO.Net
> > > > http://www.oledbdirect.com - The fastest way to access MS SQL
Server,
> > > > MS Jet (Access) and Interbase (through OLEDB)
> > > >
> > > > "YangKai Liu" <yangkai.liu@burkelee.com> ������?�������� ?��������
> > > > ��������? news:41492884$1@newsgroups.borland.com...
> > > > > I am writing codes with ADO using BCB6.  The program will be
shipped
> > to
> > > > > producttion site.  Which version MDAC is requried at the
production
> > > site?
> > > > > Should I install BCB6 SP4, will there be any change to the
required
> > MDAC
> > > > > version?
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>