Hi there,

We have a Windows 2003 server running D3 7.5.2 here in the office.
Now we want to use an application written VB.net (vb 2005) to access
some data within D3.
To do this we use the D3ClsLib.dll.
This works perfectly in windows XP, but when we run the same
application on win2k3 we get the following error: Creating an instance
of the COM component with CLSID {B577DDED-387F-11D6-9E45-0040051573B6}
from the IClassFactory failed due to the following error: 80040664

We think that the problem is that VB.net uses an "interop" of the dll
which he uses to make the dll compatible with .Net.
We tryed to reference the dll directly but it .net doesn't allow that,
because the dll isn't .net compatible.

Is there anyone who can help us with this problem???

I haven't had a change to use vb2005 (vb8?) yet, but I have included COM
class libraries in VB7.

You have to click "add references" and then click the COM tab to find your
..dll

If you'd like to email me off-group with a small sample code or picture of
what's occuring, I may be able to help.

Mark Brown


<chrlinks (AT) gmail (DOT) com> wrote

If you do email me, but VB HELP in the subject line or my spam filter might
snag it.

Mark


"Mark Brown" <mbrown (AT) drexelmgt (DOT) com> wrote

On 31 mei, 20:21, "Mark Brown" <mbrown (AT) drexelmgt (DOT) com> wrote:
The mail is on its way, with screenshot and test project.

If you're going to use .NET, I highly recommend mv.NET which is all
managed code, rather than trying to use the D3 Class Library which is
based on COM. The mv.NET "suite" has three libraries for accessing
any MV environment, including D3. One of these libraries is very
similar to the D3 Class Library and is familiar to MV BASIC
programmers.

The D3 library needs to be called via P/Invoke, which just complicates
code, and it makes .NET people think MV is old and dying techology.
Since it's not "managed" code you're subject to DLL Hell and other
deployment issues. A number of our colleagues here who started with
the D3 Class Library have migrated to mv.NET. We all started with
PDP.NET but then gave up, went to mv.NET and never looked back.
mv.NET works with the .NET Framework 1.1, 2.0, and it's being ported
to v3 now. It's well supported, constantly enhanced, and it includes
a lot of features that we would otherwise need to write by hand with
other similar libraries.

BTW, you have your terms reversed: .NET uses P/Invoke to call COM,
which is what you're doing. COM uses Interop to call .NET.

Nebula Research and Development is a worldwide distributor for mv.NET
and provides support and development services. Contact me if you're
interested in a FAQ or download info for a free trial.

Tony Gravagno
Nebula R&D
TG@ remove.this.partNebula-RnD.com

On May 31, 9:13 am, you wrote:

Hi,

BRIZ can be used as a COM server. BRIZ is free for in-house use and
with freeware. With the help of COM interface D3, OpenQM and Universe
systems can be accessed (select, read(u), write(u), transaction,TCL,
subroutines ...). Asynchronous(interactive) execution of TCL commands
and custom server subroutines are very powerful and unique tools.

Instead directly using of COM "many instances" of custom ActiveX, DLL
and ATL can be created. COM is available in VB, VBA, .NET. It is
possible to use COM, GUI and Green screen application in one session.


Regards,
Grigory

I don't believe anyone has mentioned yet but the problem is an issue
of the differences of COM objects on WinSvr2K3. They changed the
security for COM objects and it is requires much different permissions
and setup. I have not been successful at this point with other COM
based software we have tried to migrate to WinSvr2K3 so unfortunately
I can't give you the resolution but I hope that points you in the
right direction.

Dick

On May 31, 9:13 am, chrli... (AT) gmail (DOT) com wrote:

If it's a permissions problem, you may be able to solve it by updating the
service properties to start in an account/domain where the users live
instead of the default, which IIRC, is administrator.

=======================

"Thiot" <Dick.Thiot (AT) gmail (DOT) com> wrote