Thanks Roy,

>>Downloaded it, installed into a test database and the
>>system recognises its there. At that point things come
>>a bit unstuck. I don't know what functions are in there
>>so I can't test any further.

That's exactly what I wanted you to do, as that proves the DLL is compiled into a form that EDB recognises & ought to be OK.

Now I am really confused why my system won't recognise it!

Scratches head.

D'oh.

Dll was compiled for the Default character set (UNICODE).

My DB is ANSI, so cannot be registered.

... I guess I have to reset the character set of the DLL & recompile ... doesn't look too hard to do this.

OK. Double D'oh.

Feeling useless ... there does not seem to be an obvious way to "switch" the DLL project to ANSI from UNICODE.

I have removed references to UNICODE in the DLL source.

I can register the DLL in a UNICODE session, but not in an ANSI session.

In a UNICODE session when I try to run the module I get the error (#202) "The module was not compiled to use the ANSI character set"

So I think my error is in the compilation, i.e. the module is not set up right character-set wise, but I can't see how to put it right.

On 3/23/2016 9:57 AM, Adam Brett wrote:
> So I think my error is in the compilation, i.e. the module is not set up right character-set wise, but I can't see how to put it right.

Tim had just said to use EDB_UNICODE compiler define for unicode version
and not have it defined should default to ansi.

Raul

Adam,

Please email me your external module project, and I'll take a look and tell you what the issue is.

Tim Young
Elevate Software
www.elevatesoft.com