This may seem like a silly question but can somebody give me the definition of a Baan "object" I always thought that the word object was a general term for forms, reports etc. But when you look at the file structure under $BSE/application objects seem to be something in their own right, $BSE/application/tdB40_c4/otdsls.

Please enlighten me as to what an "object" is

Thanks

PJ

An object is a "compiled" baan program. It works on the virtual baan machine. It is the same concept than for Java. You can compare a baan object to a java class.

A baan object is no dependant of the server OS. So you can take an object from an NT serveur and put it on an Unix server and it works very well (according you use the same version of baan).

Once again, exactly like java.

PJ,

It's all in a name. Some people would call each file under $BSE/application an 'object'. However I believe to be more correct you can talk of 2 types of objects: report objects and session objects (both start with the letter 'o'). The 'objects' are the runtime versions of the source scripts and reports. Likewise you have form sources + forum dumps etc.

A session on itself does not exist. A session is composed by several Baan components.

An object in Baan is what you get when you compile a Baan component (or by other words, all that is compiled - not dumped!):
- scripts (program / libraries) + includes
- reports

From this ones you have (what I call the "real" ones) objects (p-code), the compiled scripts, and the "other" objects, the compiled report.

Victor,

You are right. I should not have used the term 'session' as such :)

Let me see if I've got this right.

If I have written a program script and then compile I get an object, if I write a report and compile I get an object. Do both of theses go into the same object? i.e. osls4102 could hold a compiled report and a compiles program script.

PJ,

No they are 2 different objects. Consider your $BSE/application/tdB40_c4 directory for instance:

Checking on tdsls4404 objects:

./otdsls/osls4404 ----------> program object
./otdsls1/osls4404010001 ---> report objects for language 1
./otdsls1/osls4404020001
./otdsls1/osls4404030001
./otdsls2/osls4404010002 ---> report objects for language 2
./otdsls2/osls4404020002
./otdsls2/osls4404030002
./otdsls3/osls4404010003 ---> report objects for language 3
./otdsls3/osls4404020003
./otdsls3/osls4404030003
./otdsls4/osls4404010004 ---> report objects for language 4
./otdsls4/osls4404020004
./otdsls4/osls4404030004

I think it's safe to say that I now understand what an object is.

So would the logic be that a Baan session will call an object which in turn will call the program script\report contained within its compiled form?

Thanks for all your help!

PJ

To finalise this "object", I'll just add the following:

- Compiled scripts are not language dependent.
- Compiled reports are language dependent.

You notice what is what by looking at the directory (using Patrick's example):

./otdsls/ - no number, contains language independent, compiled scripts!
./otdsls1/ - with language number, contains compiled reports for language 1
./otdsls2/ - compiled reports for lang. 2
./otdsls3/ - compiled reports for lang. 3
./otdsls4/ - compiled reports for lang. 4

A session must have an object (compiled script), but only has a report object if it is a print session type. So the answer to your last question is yes :)