"Chirag" <Chirag@discussions.microsoft.com> wrote in message
news:C7532C65-35B1-4BE2-9C92-F19CBACB976B@microsoft.com...[color=blue]
> Hi Sven,
>
> Most probably you are developing a DLL that exports the functions API
> directly as Windows does.[/color]

That is a very precise description of my dll
[color=blue]
> You can provide them with the function signatures that they can use to
> directly call the DLL functions.[/color]

I have done that
[color=blue]
> The registering thing is required for DLLs that host ActiveX objects and
> Automation interfaces. It seems your application developer is trying to
> use your DLL as if it has ActiveX objects in it. You need to tell them
> that your DLL is not hosting ActiveX objects unless you are actually
> creating ActiveX library.[/color]

Right.

and thanks, Sven
[color=blue]
>
> - Chirag
>
> PowerShow - View multiple PowerPoint slide shows simultaneously
> [url]http://officeone.mvps.org/powershow/powershow.html[/url]
>
> "Sven Pran" <no.direct@mail.please> wrote in message
> news:OBylKIrrIHA.552@TK2MSFTNGP06.phx.gbl...[color=green]
>>I have an appcation that includes a dll I have written and which is of
>>interest to other application makers.
>>
>> One of them has written an MS Access database application using VBA, he
>> wants to use my dll and approached me telling me that he could not
>> "register" this dll so he could not call it from his application.
>>
>> I do not know anything about registering dll modules, my installation
>> program (INNO) simply installs them to the windows\system folder and
>> that's it. (I have wondered whether to install to \system or to
>> \system32, but as long as \system works I'm happy about using that)
>>
>> Can someone enlighten me on what this is all about?
>>
>> BTW. My application is written entirely in Delphi and all my dll
>> functions use standard linkage, exactly the same as is used for Windows
>> API functions.
>>
>> grateful for any information.
>>
>> regards Sven[/color]
>[/color]