Re: LibFunc from VB

rullbandspelare · Post by **rullbandspelare** » Wed Jan 23, 2008 9:06 pm

In responce to my question regarding a DLL that requires record data type.

When you pass values to DLLs what you actually pass are references to memory locations. Macro Scheduler can only talk to DLLs that accept integers and/or char pointers (strings). Your function requires a custom type - a record. It's VB specific.
_________________
Regards,
Marcus Tettmar
Blog: http://mjtnet.com/blog/
Please do not email or PM me with private support requests - post questions to the forum so that everyone benefits. For fast, guaranteed private support please send email via our web site.

So, what are the best workaround for this? Should i just try to compile the DLL function whithin Visual Basic and feed the result to a file?
Is there any plans for enhancing MacroScheduler to handle this?

Thanks!
/tomas

Post by **Marcus Tettmar** » Wed Jan 23, 2008 9:19 pm

It's not a question of enhancing Macro Scheduler. Your DLL is probably only compatible with VB.

Macro Scheduler can only be compatible with standard DLLs created with the stdcall calling convention. Basic string and integer types are required.

The workaround would be to recompile your DLL to make sure it is using the standard (stdcall) calling convention and instead of a record type specify each of the strings separately in the parameter list as individual parameters.