<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body>
Ouch! Talk about riding into a blind canyon. I can, however, see where this would be hard to accomodate while there is so much BOR still out there. I'll have to retrofit some, but all in all I really like working with the classes much better than the BOR. <BR>
<BR>
One could create a custom BOR with a method that is a wrapper for the class method and make that method the default.<BR>
<BR>
Thanks,<BR>
Ed<BR><BR>> Date: Mon, 25 Jun 2007 16:43:08 +0100<BR>> Subject: Re: ABAP OO problem<BR>> From: asap@workflowconnections.com<BR>> To: sap-wug@mit.edu<BR>> <BR>> Correct, that's not available. To be honest, I don't use Adhoc Objects<BR>> much, most of the time the object types are known and you can just as well<BR>> create container elements for it.<BR>> I haven't played much with the ploymorphic capabilities of OO in WF, but<BR>> it may well be something as simple as creating your own 'Adhoc' object to<BR>> which you can bind whatever you like.<BR>> <BR>> <BR>> On Mon, June 25, 2007 3:35 pm, Edward Diehl wrote:<BR>> ><BR>> > Well, I found one big drawback to using classes. You cannot assign a<BR>> > created instance to _Adhoc_Objects. The error message is CL and BO are<BR>> > incompatible.<BR>> ><BR>> > Is there a way around this? The CL has a default method to display<BR>> > certain info and is essential to meet the functional requirements.<BR>> ><BR>> > Thanks,<BR>> > Ed_______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> ><BR>> <BR>> <BR>> -- <BR>> Mike Pokraka<BR>> Senior Consultant<BR>> Workflow Connections<BR>> Mobile: +44(0)7786 910855<BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR><BR></body>
</html>