Guzzisto
13th May 2002, 12:17
A user needs to start the same session for different companies several times per day (e.g. Maintain Receipts). Off course this can be done by logging on twice (need more licences!) or changing companies all day.

Is it possible to pass a company number to a session either from the Baan menubrowser or the Baan desktopbrowser? Or any other trick?

alejandro
13th May 2002, 12:37
If you have code:

Copy the session to a new customized session
Put in before.program section:
long new.comp
new.comp=lval(argv$(1))
switch.to.company(new.comp)

You can execute this new session from menu browser with parameter company number.

You do not have code:

Create a new session:
(session.st = session you want to execute in different companies)

new.comp=lval(argv$(1))
switch.to.company(new.comp)
wait.and.activate(session.st)

Also you can call this session form menu, execute program...


Which method is better you decide. Sometimes if there is a zoom process from a session, the session name that called the zoom process is in the code of this zoom proccess, so if the session name is different, things will not work right.

You have to try and then decide.

Hope this help.

victor_cleto
13th May 2002, 14:11
There's a discussion related to this already, see the thread http://www.baanboard.com/baanboard/showthread.php?s=&threadid=852&perpage=5&display=&pagenumber=2
There is an example there (implies coding).

Running sessions for multiple companies need to be done thru the normal ways (use multiple BW's, change company within Baan). Since the other options involve coding, this thread is moved to Tools Dev.

julisb
13th May 2002, 14:28
Hello,

if you only want to play between two companies and for some sessions, you can use the key map settings.
Nevertheless in which you are playing at present the key map settings always search for the user's starting company from the user masterdata.
E.g. in the user settings he starts with company 601. Beginning of the day he change to 602. When using a key he will get the session from company 601.
Might be a bug, but in our system it is like that.

Regards, Juli