Hi

I have an issue calling stored procedures in external modules.

For testing purposes, I created an external dll which contains a procedure called 'Test' and all it does it returns an integer value '1234'. For that, I
used one parameter called 'Result' of type integer and InOut.

I stopped the server, moved the dll file to server's config folder, restart the server and used the manager to add the procedure to the database. All
is fine

Regardless where I execute the procedure from (whether from the application or from the manager), I get the message

ElevateDB Error #9999 Access Violation at ..... in module 'edbsrvr.exe'. Read of address .....

I built the server on my machine to be able to debug it (I had to remove a reference to a non existing file called 'FastMM4' from the project source).
I found the the access violation is raised when calling PrepareParams inside the following procedure . The reason is that 'Tokens'
in ...Definition.Tokens.ArgumentTokens.... is NIL.

procedure TEDBLocalProcedureManager.Prepare(const ProcedureToPrepare: TEDBString);
begin
  FRoutineManager:=DatabaseManager.OpenRoutine('',ProcedureToPrepare);
  PrepareParams(FRoutineManager.Routine.Definition.Tokens.ArgumentTokens[ROUTINEPARAMS_TOKEN_POS]);
end;

Please advice me (any help or fix will be very much appreciated as I'm very late in delivering the project for translation)

many thanks

Alfred

Alfred,

<< I have an issue calling stored procedures in external modules.

For testing purposes, I created an external dll which contains a procedure
called 'Test' and all it does it returns an integer value '1234'. For that,
I used one parameter called 'Result' of type integer and InOut.

I stopped the server, moved the dll file to server's config folder, restart
the server and used the manager to add the procedure to the database. All is
fine

Regardless where I execute the procedure from (whether from the application
or from the manager), I get the message >>

Yes, it's a bug.  1.03 should be out by Thursday or Friday, and it will
correct this issue.

--
Tim Young
Elevate Software
www.elevatesoft.com