In a session I'm using the functions stpapi.put.field and stpapi.find.
When the session is run by a user working with the menu browser,
no problem, it is working perfect.
But when a user with the dem browser runs the session (with exactly the same authorizations), the session hangs on the stpapi.find command and give the next message:
Fatal error: object 0 in process 14 not found,
proces 14: Fatal error: process terminated by display server.
Can anybody help me please?

I do not know a whole lot about the DEM browser, but we use DEM's at our site and the stpapi commands do work. So maybe you just need updated DEM objects or tools objects.

Some questions - Can the DEM users call the sessions that are in the stpapi commands? Are they in the same company and VRC? Same version of Baan(client also)? Have you tried recreating the DEM Desktop for the users? If yes to these questions then I do not have a clue as to what is causing the problem, but I will be interested in what the solution is. Sorry I am not much help.

Good Luck!

Mark

Thanks for your reply!
Yes, the users wich gets the error,
can start the session without problems if it is present in the DEM browser. It is the session tpptc1509m000 Baan ERP, I believe version 5b.
As soon we change the same user to menu browser, the session with the stpapi command runs perfect.
But when the same user is working with the DEM browser, the session crahes again.

This session wich is called by the api creates records in tpppc109,
for the whole project structure.
So, I don't have to program this by myself, if the api command works also with the DEM browser.

If there is someone who knows more about the combination of api and DEM, please let me know.

Now I know, that not all api commands are crahing in the DEM browser. Thanks!

Hi,

We faced similar problems while calling api calls from dem. We were calling DLL functions and in this DLL functions we were calling API calls.

To Resolve this problem. We created 3GL Object of the DLL and instead of giving call to DLL directly we called this 3GL Object. We donot have such problems now.

If you need more details please let me know.

Regards,

Yes, if you can give me more detail, please!

What do you mean by: create a 3GL object from the dll.

We don't use a dll for the api calls.
The stpapi commands are directly in the program script.
Also the called session don't use dll's as far as I know.

Thanks;

I did not have a clue about that possibly being the problem. Anyway I always use ttstpcreatdll to create a DLL script for the session that I will be calling. None of my functions servers actually use the stpapi commands, they are in the DLL I create with ttstpcreatdll. I then just attach the dll to the session script.


Mark

There is a solution for this problem, at least some problems between afs and DEM has been solved.

THe solution is built in the ttstpstandard program.


The defect number is 117081


Bye

in one of the latest standard programs, if I remember well its solved in the standard program of early february. jdhaan works at the same project as I do so I can assure you that this is solved.

Rgrds,
Han

As you can read in the last messages, the problem was solved by an update of the standard program.

No changes were made in the stpapi commands,
the program works perfect,
also when it is running from the DEM browser.

Thanks for all replies.

Just a note pertaining to using stpapi calls in sessions located on the DEM browser. If you generate session authorizations via DEM, some users will get permissions errors when running the custom session, if they do not otherwise have access to the called sessions.

One way around this is to make a manual entry in ttadv237 linking the script of the custom session to the called session. Then when DEM generates, it will read this entry and provide the appropriate authorizations.