monica1
21st December 2005, 12:37
There is any way to compile a program with debugger but that only one person can see the debugger and for the rest this program continue without appear the debugger screen.

Thank you in advance,

EdHubbard
21st December 2005, 12:57
In Baan 4 on the Baan Windows configuration screen you can set up on each user not to see the debugger.

In the box Bshell environment "Command" you would enter something like
-- -nodebug.

monica1
21st December 2005, 13:00
And on the contrary not it can? Because there is 100 user that I don't want them to see the debugger while I see the trace.

EdHubbard
21st December 2005, 13:03
What I meant was that you would need to go to each users desktop to set up their bw so they could not see the debugger. As far as I know by default all users see the debugger otherwise.

Ed

monica1
21st December 2005, 13:04
Thank you very much

beginer
21st December 2005, 13:05
Hi ,

You being on UNIX environment.....
I suppose can modify the profile file for achieving the same.
I don't exactly remember which user file u need to modify.

Han Brinkman
21st December 2005, 13:07
These is way but not an easy one.

Check which package combination you use. Open the fd<package combination> file in ${BSE}/lib.
Copy the line that represents your object e.g. otd. Change the first line of these two and insert in front of it your name with curly braces around it. Add a path in front of the normal path. You can place your object compiled in debug mode there.

Please note that a convert/create runtime will remove your manually added entry.

Furthermore note that you need to be carefull, you can end up with a 'crashed' environment. I guess you want to test it first in a non production environment.

Han

JaapJD
21st December 2005, 13:07
You can put the debug object and source somewhere else and modify the fd file temporarily. Create an extra entry for p<package> and o<package> preceded by your login between brackets. Example:
{<login>}o<package>:${HOME}/debug:${BSE}/application....
{<login>}p<package>:${HOME}/debug:${BSE.....

In ${HOME}/debug you have to create a subdirectory with name o<package><module> and put the object there. The source must be in ${HOME}/debug/p<package><module>.

NPRao
21st December 2005, 21:01
Monica,

I noticed you are on UNIX, if you have SCM enabled for the VRC, then you can just check out the script and compile in debugger, which is visible only for your login or the SCM group (if shared with others).

monica1
22nd December 2005, 09:26
CAn you explain me how to do that?

Francesco
22nd December 2005, 20:29
As a matter of fact, I used the same method to test single objects provided by baan support.

The problem with SMC, apart from being a pain in the lower back to install, is that you change your entire development environment. You will also have to install version control on your UNIX because that is what Baan really uses.

NPRao
22nd December 2005, 21:04
The problem with SMC, apart from being a pain in the lower back to install, is that you change your entire development environment. You will also have to install version control on your UNIX because that is what Baan really uses.
I have to differ with Francesco, I would rather install an SCM VRC as a safer option and one time effort, compared to letting developers messing with fd files and making a mistake with the structure inside it.
Monica, you have a setup a new check-out/derived VRC and link to the development VRC. Refer to the sessions in the Menu -> Tools -> Application Development -> Software Configuration Management (SCM).