Does anyone know how to lock out access to the user for changing the .bwc file? You can really do some damage with that command line option.

According to Solution 19276 on the support site, it says it requires a reg entry. The Password lockout works. The other option to lockout the configuration file does not for the Baan IV GUI (the solution will be updated by Baan Support to correct this).

Has anyone had any luck with locking out access to change the .bwc configuration file?

Thanks!

Even if you change permissions on the .bwc file to be only readable, that does not invalidate changing it after it has been read, you cannot is just save it.

The blocking must come from disabling the "Configure" button, so application related... I think you're stick with that solution and if it does not work (haven't tested it yet) wait for the next solution.

I don't think Baan will do any solution to fix this problem. The solution works with the Baan V GUI, but they aren't going to fix this one. Boooooooooo!

But, be sure to check out the solution. It does allow the password to be blocked.

I have looked in the registry and do not find the Baan BW in the policy location.

Any suggestions?

make the file attributes to read only.

I would suggest try the implementation of a wrapper script solution. In the ipc_info file make an entry for the common bshell file that does not point to bshell6.1 but to wrap_bshell. In the script you can start the bshell6.1 with your own options... I think the command line options from the client are not passed...

You have to test this because I am not really sure this will work out right for you.

if u try the steps given in the sol no 9900 on baan support site, it will create the reg key automatically. U have another sol to change the permission of that bwc file and take out the authorizations from the normal users(only in NT).
Hope it will solve ur probl.

~BaaNLover

Thank you I had found the solution at Baan Support and I was able to prevent changes to the configuration.