I am trying to write what I thought was a simple report using the ManagerO
universe in which I select the following 3 columns from the Join class:
Table 1 Name, Table 2 Name, and Join SQL. However, when I try to run the
report, it tells me that the objects are incompatible. If I set the universe
options to create separate joins for each context, then I get unrelated
results.
I’ve looked on the BO CD, and other than the ManagerO universe, there
doesn’t seem to be any documentation. So, can someone explain to me why this
data is unrelated, since the Table 1 Name and the Table 2 Name are the same
as what is displayed in the Join SQL? (I could just select the Join
SQL;however, I wanted to display the separate name columns for easier
reading).
The “ManagerO” Universe simply has alot of errors, among them wrong contexts for
the “joins” evaluation. I’m working on an “enhanced” version of it for BusObj
4.1.x. which gives you also the complete pathname of objects, correct
WHERE-clauses of conditions and detailed info on object properties…
Walter
DI Walter Muellner
Delphi Software GmbH, Vivenotgasse 48, A-1120 Vienna / Austria
Tel: +43-1-8151456-12, Fax: +43-1-8151456-21
e-mail: w.muellner@delphi.at, WEB: http://www.delphi.at
Hey Walter! I wonder if you’re still listening. Enjoyed seeing you in Miami! Never been so shocked as when I read your name tag .
Has anyone done what Walter planned…identified the pieces and parts of the ‘Object Properties’ object in managero? I’ve gotten the obvious ones (data type, qualification, and projection), but need help with the rest. If nobody responds and I get bored ;-), I’ll do it myself.
Also, I’m having an instr mental block. That should get Dave’s attention ! I want to pick apart object properties from the first comma + 1 to the next comma - 1…
as when I read your name tag 
.
! I want to pick apart object properties from the first comma + 1 to the next comma - 1…
(BOB member since 2002-06-11)
(BOB member since 2002-08-22)