I have just compiled an Active X dll (first time). I have only added a single procedure to the dll and I am passing data in and out of the procedure using types.

I confirmed the code worked at module level in my client program, copied the procedure into an Active X class module along with the type definition info and compiled the code - no problem.

To get at the new external procedure (having deleted the original in my calling code) I used a declare in my calling code that pointed to the dll as "C:\dlldirectory\newdll.dll" - note I had not registered the dll on the system at this time.

This seems to work OK - the file is recognised when I run my calling program - but I get a "Can't find entry point..." message back. What am I doing wrong? Do I need to include some packing procedures that VB needs??

Any help here would be damn usefull in my visualisation of the cosmic all - thanks in advance.

PS - even registering the DLL didn't get around the problem.