>>Why does your component name and your class name the same?
>For no particular reason. Is there a problem with that?

We can't do this in VB. We can't name a class the same name we title the project!

>>If so, what is the instancing property value?
>I don't understand this question.

Since it is a VFP component, you probably don't have this property!

There are 2 kind of DLL:
-Automation DLL (like Excel, Word and all the other).
-Library DLL (like User32, GDI32, Kernel32 and all the other).

The difference between both is that those using Automation can be instantiated using the New (or CreateObject) keyword.

Library DLL are only a file containing functions which can be used from VB and other languages.

For example, this declaration allow you to use the WritePrivateProfileString function from the Kernel32.dll like if it is a VB function:
Declare Function WritePrivateProfileString Lib "kernel32" _
Alias "WritePrivateProfileStringA" _
(ByVal lpApplicationName As String, _
ByVal lpKeyName As Any, _
ByVal lpString As Any, _
ByVal lpFileName As String _
) As Long

So my question now is: Can VFP build automation DLL or build library DLL?

Éric Moreau, MCPD, Visual Developer - Visual Basic MVP
Conseiller Principal / Senior Consultant
Moer inc.
http://www.emoreau.com