Hi Pamela
<i><font color="#663300">What regular conventions are those? I have never used the BO builder, so I am not sure how it works, but does this BO have a DE class defined in aDataEnv?</font></i>
Yes and Ed has done a good work of it, it works 2 ways modify the aDataEnv and the builder reflects and use the builder the aDataEnv is updated.
<i><font color="#663300">The bizobj's data environment class depends on finding a view defined in the app's primary DBC. An SQL statement in the Init event of an object does not create a view. CREATE SQL VIEW AS SELECT Yada, Yada, Yada does, but there is no point in running that statement every time you initialize an object. Just do it once and it is stored in the DBC, that's what a view is all about.</font></i>
Beat you by 9 hours, ie. before I read this :-). How about multiple SQL cursors based on different sets of data which don't readily join, joined into one SQL View, is it possible?
Feels good to receive help form the forum again. Thanks Pamela and Lynette for answering both my queries.
<i><font color="#663300">Hi Bhavbhuti,
<i><font color="#663300">Fired the builder for this BO and set up the DE using the regular conventions.</font></i>
What regular conventions are those? I have never used the BO builder, so I am not sure how it works, but does this BO have a DE class defined in aDataEnv?
<i><font color="#663300">Error instantiating cursor object.
Cannot find lv_LKTrialBalance in c:vso3projectsc00datavso2views.dbc</font></i>
The bizobj's data environment class depends on finding a view defined in the app's primary DBC. An SQL statement in the Init event of an object does not create a view. CREATE SQL VIEW AS SELECT Yada, Yada, Yada does, but there is no point in running that statement every time you initialize an object. Just do it once and it is stored in the DBC, that's what a view is all about.</font></i>
Regards
Bhavbhuti
©2002 Bhavbhuti Nathwani |
