Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Basic COM question
Message
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 9
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01057884
Message ID:
01057908
Views:
7
It has nothing to do with COM, but the way macro expansion works. When VFP sees the ".", it stops doing the macro expansion.

>Hi
>I have the following construct in my web service:
>define class basecom as Session
>  procedure Init
>   ***blablabla
>  endproc
>  procedure Error ( nError, nMethod, nLine )
>   ***bla bla bla
>  endproc
>enddefine
>
>define class myWS as basecom olepublic
>  procedure myfunction1( inxml as String ) as String
>   *** bla bla
>  endproc
>  procedure myfunction2( inxml as String ) as String
>  *** more bla bla
>  endproc
>
>  procedure myDispatch( DispXml as String )
>   *** DispXml contains a command clause ( "myfunction1" or "myfunction2" )
>   *** and the xml parameter to send
>   *** so we strip those from dispxml, say to lcCommand and lcXml
>
>   lcCommand = "This."+lcCommand+"("+lcXml+")"
>
>   lAnswer = &lcCommand &&& <-- this call fails
>
>enddfine
>Why the call fails? Shouldn't it call the other functions using This. ? Is there another way to get a pointer to the created com object?
>Thanks
>Jaime
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Previous
Reply
Map
View

Click here to load this message in the networking platform