Hi Tim,

Found the problem. When creating a new ElevateDB External Module via the New
Item template (in RAD Studio 2010), the method signature for
EDBExternalModuleRoutine is incorrect (parameter is a String rather than
AnsiString) causing the modules OnRoutine link to the method to be removed
... obviously when this happens the event handler is never triggered, doh

Slow going, but the penny dropped for me eventually

Best regards

Steve


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:107A880D-DC7A-43DA-A2E8-F5D54A1E8237@news.elevatesoft.com...
> Steve,
>
> << I will bundle it up and send to you tomorrow. >>
>
> Thanks.
>
> << This is not a high priority so don't worry about a quick answer. >>
>
> No problem.  I'm getting a new build ready by next week, so I can squeeze
> it in there.  I'm sure the fix is simple.
>
> << For example I have added the following functions today >>
>
> Cool.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Steve,

<< Found the problem. When creating a new ElevateDB External Module via the
New Item template (in RAD Studio 2010), the method signature for
EDBExternalModuleRoutine is incorrect (parameter is a String rather than
AnsiString) causing the modules OnRoutine link to the method to be removed
... obviously when this happens the event handler is never triggered, doh
>>

RAD Studio still has issues with identifying AnsiString vs. WideStrings when
automatically creating event handler templates in the code.  I always have
to be careful when modifying the external modules that we ship with
ElevateDB because of this - the IDE always wants to remove them because it
doesn't know what to do with our TEDBString type that we use for abstracting
out the AnsiString/WideString differences.

--
Tim Young
Elevate Software
www.elevatesoft.com

Steve


Well done that man <vbg>

Roy Lambert