Hello.

Whan conceptual question which will help me a lot is:
What's happened when we link language dependant software component to component in original language (2)?
(I do not copy or move nor overwrite component)
For example:
I link report in my (Croatian) language to original report in English.
When some changes appear in original report - do I have to start "link SW compo. to original language ... " AGAIN, or I can only compile to make it apear OK in my language?

The same question is for other language dependant SW components?

Thanks
Book

Hope the following notes help:

Linked to Language field helps to maintain report layouts and reports in one main language, using labels. It eliminates translation of the report layouts, so you avoid having to paint the same change in the two different languages. Only the Report Description and the Labels need to be translated. Maintenance of reports becomes much easier in this way.

The same concept apply to forms.

Labels, messages and questions have to be created in the individual languages anyway.

Thanks,
it's ok, but
I found in Baan documentation that copy and link are not the same things - are they or not?
Baan said that with linking I save disk space - is it true ?
When I compile linked report do I realy compile peace of original + language dependant part and get object in my language?
or I copy whole story and get object (where is there saving space?)

And,
when we get report from Baan (is it in binary form? or in source?)
does my link breaks (or it is copy and link is kind of typefehler)?

Is there a documentation on this subject to clear things up.
(I now look into unix with ls -lau to see if something is copied/moved/linked/partialy linked/nothing if overwrite not allowed...
with this so trickie session ttadv6200m000) ...
and help said ... treat with care ...
And, I have to say - it is one of basic things to know when administering Baan - but so confusing and secret ????

Thanks again
(can't wait to see reply)
book

The reports (language dependent objects) do consist of several parts:
1) The layouts (borders, lines, space, position of lables etc)
2) The variables that will be filled with the data
3) Logic on the report for calculating sums etc
4) The data in the lables (which are language dependent)
5) The data in the variables (which can be language dependent)
etc

Some of these are strictly not language dependent (1, 2, 3). These take diskspace, but in the database.

Others are language dependent (4) they are in the database.

Obviously the data (5) is never written to the object itself.

When you link to other language, only the (mother) layout is changed when you change something in the type 1-3 parts. There modifications are stored in the native language of the report. All different language reports will be look-alikes.

When you copy to other language, all of the (language independent) parts are copied to the other language. The layout of the report can be made completely different from the native language.

All the parts 1-4 are compiled into one language dependent object. Part 5 is added at runtime.