I found, that under some circumstances, it is possible to compile and edit the standard (B40_b) on our system.

Does somebody know, where I can find out, why that is possible?

Thanks in advance
spartacus

Theoretically, this is not possible without a developers license. And if you have not had the proper training or knowledge doing so can be very hazardous to your system.

Yes, I know that shouldn't be possible, but it is! Therefore I would like to find out how to correct this.

spartacus

Did you at any time have development access ie during implementation. It could be that without knowing you do have a development license left over from some work that you had done.

It was my understanding that as long as all of the pieces(DLLs, source, etc) were there and you had permissions to that VRC you could compile it. I have access to all of our VRC's, but I never try to compile in one of the Baan layers. Right offhand I can think of two ways to fix this - do not give anyone permissions to the B40_B VRC or two change the permissions on the directory structures so that compiles can not take place.
On our production system only BSP can compile or make changes in other layers. They did this through the directory structure - only BSP has write access.

Mark

Well, it should be the case that you cannot edit the standard, compile is available (otherwise you could not do RDD for tools), but unless you have development licences you should not be able to edit the standard in any way.

You keep mentioning "developers license" and I am not sure what you are talking about. At one point in time I was told that all we needed to do was to buy source code and we could compile any of the Baan sessions. Even though we are on 4c3 A&D some of the session still run from the standard layer. So what exactly is this "developers license"?

Thanks

Mark

Buying source code is almost the same thing. You can buy a single license that allows you to alter the standard ie become a developer. I beleive that you can also buy indiviual source codes to allow you to alter just that session or object. The developers license just allows you to do it to everything. These are normally bought for large scale customisations as its easier to 'mess' about with the code on the system rather than development done off site then moved.

And you would find that if you had some serious customisations done that you would still have to run them from the standard that was customised to keep functionality upto date. Being on 4c3 I can imagine that you will have to take you customisation into account should you ever consider upgrading!

A Developer license will NOT allow you to modify the standard.
If yout want to do development in Baan, you can buy a "Developer License". This is (was?) licensed seperatly from the main product. It allows you to access the Menu Tools/Development and the sessions within (like Maintain Tables, Maintain Sessions).

This has nothing to do with source code: You can also buy an (extremely expensive) "Source code license" that gives you access to ALL Baan Sources except the Tools sources.

Without that Source code licence, you normally should be able to purchase single sources via your Baan partner. You need a source if you want to modify that Baan standard session. You don't need a source for doing development (apart from include files).

Still, even when modifying a standard source, you will not modify the standard, because you are doing the development in a seperate software version, derived from that standard.

ONLY BAAN DEVELOPMENT may actually modify the Baan "Standard" software versions. Some letters in the Package VRC indicate a standard VRC.

If you were able to modify the Standard, then either

- you're on a system that somehow behaves like one of Baan development (don't know why...)
- or probably you didn't really modify the standard, but "overrided" it with a modified standard
- or you have an incorrect PMC setup. I've seen one case, where you could actually modify the software that came within a patch,
because somehow this was not recognized as "standard" software any more.

Hope that throws some light on the matter of licenses...
Uli

This maybe a matter of language. When I have been dealing with anyone from Baan it has always been called a 'Development License' that allows you to edit the source code and has always been expensive. But was always under the impression that it allowed you to alter the standard as well. If this is incorrect then I appologise as I was only working on the information given to me as I have never used a system with the license.

We are talking about an b2 System, which is set up long time ago from somebody else.

At a normal system it is not possible to switch to a "released" VRC as "B40_b2". That is also not possible here. But strange if I am in B40C_b2_001 it is possible to compile an edit a "B40_b2" Source.
The structure is something like:

B40_b
B40_b1
B40_b2
.
.
.
.
.
.
B40C_b2_001
B40O_b2_001

From B40O_b2_001 it is NOT POSSIBLE to compile and edit the standard, but from B40C_b2_001.


About these discussions compiling sources: The (my) normal way is: Buy a source from Baan, put it in the related STANDARD-VRC, copy it to a customisation VRC, compile it!!!

Ravenscross: Is there any way to check if there are any developer permissions on the system?

thanks
spartacus

Not quite sure there is. I think (from information given to me), that you create a user that can only have those authorisations. As this is all what I have been told (and by more than one person!) I cannot say, as I have not used a development/editable system before.

However you do say that you buy the source which would make it open.

OK let's summarize:

I have a system where I can compile, modify, copy sources. That is quite normal, because I am working in Baan Tools.

But it is not normal that it is possible to modify something in a VRC of a "released standard". Also developer / superuser has normaly no permission to do that. On that system it is possible, somehow.

Now I will appreciate any hint which helps me find what going wrong, that it is possible to modify the STANDARD

Thanks a lot
spartacus

Originally posted by spartacus

Ravenscross: Is there any way to check if there are any developer permissions on the system?

thanks
spartacus

I would check in ttiex3500m000-Display Requested System Configuration, where you should see the "Development Tools" as one of the (Runable) Commercial Functions. But, I am not quite sure, if this is what you are looking for?

Ram.

thanks RAM.

This is not the question. Meanwhile I know that "developer permission" is what I call the "Tools licence". This has nothing to do with my problem.

greetings
spartacus

There is a setting in session Maintain Tools Parameters -ttadv0102m000 which can be set to allow the standard to be changed.

I would guess at some stage that this has been set on.

This session is password controlled and I suspect that this is something support would need to do.

Regards
Neal Matthews
Intier Automotive - IT Support Analyst

Lets throw some light into this thread:

- A normal Baan installation does not include any source code [developer license];

- You have to buy one or more developer licenses to have access to the source code. The source code is the standard (+updates, see below) for all modules except for the tt (tools), where source code is not available (some partners have it for developing their own tt tools, like Bull);

- You have to request the source code CD from Baan, this CD needs a key to unencrypt the source dumps (that you request from Baan and they will check if you bought a developer/source license!) to be able to install the sources [thru a normal import];

- The best way is to determine if you will develop when you buy the Baan software, because you request the CD and install it before you initialize PMC and start installing service packs and so on, so that you update your [installed] sources as well;

- For the users that will develop (super users type), they must be given grants to the pVRC and modules, using the sessions under Tools -> User Management -> Developers Data (usually bsp is the owner of the password for developer authorizations);

- Developers can change anything in any layer except the layers that are "standard", like B40_c4. I noticed that the rule is that it does not allow a change of any layer that does not have a customer extension (if you build your own B40C_c4 it will not allow you to change it because it lacks a customer extension, so be careful with the names of your own layers!)

- You change [the standard indirectly] by copying the sources to your own layers and change them there. It is not good practice to change anything in the layers where the standard [+updates] are located!

I'll finish by saying that, related to change directly the sources of the standard layers (but why would you want to do that?), there is a way, of course, to override this rule (check [hidden] session tttadv0102m000 :) )

Spartacus,


you may check table ttadv002 with some tool that ignores the Baan access restrictions for that table (ODBC or Crystal, because General Table Maintainance will exit if you try to use it on that table)

There is a field "upds" indicating if Standard modifications are allowed.

Hi Neal , Ulrich,

ttadv002 seems to be the right place to check. Only I have still the problem to access these table. At the moment I have no tool/expirience/password. I tried some "standard Baan" passwords which all don't work.

Due to the fact that this system is at it is, for a couple of years I will not spent to much time right now. But I will keep track on this. If I find a possibilty to get access to that table in the near future I will post what I find in this thread.

Thanks
spartacus

Spartacus,

What the status of the VRC of the 'standard' software?

Han

Hi Han,


It is released ;-)

greetings
Spartacus

Hi,

As far as i know, if you want to compile something, there should be a package-combination connected on that specific VRC.
If there isn't you'll get an error.

GN

I've been looking at your VRC structure.

B40_b
B40_b1
B40_b2
.
.
B40C_b2_001
B40O_b2_001

The first three VRC are our standard and these should be editable (which they arent), the your B40C_b2_001 is for customersations (according to baan naming conventions the C means customer vrc). Then my guess is that B40O_b2_001 is your operational VRC, which means that your company is linked to this VRC.

Before being able edit and compile you should also set current package vrc to the vrc your components is in, seems like your current is B40C_b2_001, which is fine, becuse most of your customized sofwarecomponents probably lies here.


As a final note, if you look in your baan tools menu theres a submenu called Applications Customization and maybee one called Application Development.

Applications Customization is allways on your system, if you bought developer rights Application Development is also installed.

Actually Applications Customization is what you could call a Application Development light menu.

/Claus

Just thought I would let everyone know that according to Baan, just naming your VRC's incorrectly could allow you to make changes in Baan standard VRC's.

This is the message I received from our sys admin:
When Mark found that the domain for the contract number had somehow been changed in the base A&D layer of company 555 a few weeks ago, I contacted BaaN to see why we were able to make changes to the base A&D layer. They told me that our package VRCs were improperly named. For example, package VRC tiB40C_c3_22b0 is comprised of package "ti," version B40C, release c3, and customer extension 22b0. To protect the package VRC from being changed the version should have been "B40 " (no "C").


Mark