Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
App/Exe Build Problems when Com Interop Involved
Message
From
11/08/2009 12:17:26
 
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Desktop
Miscellaneous
Thread ID:
01417325
Message ID:
01417335
Views:
61
Thanks that worked! I thought that without it the events wouldn't fire...but they do!


>Hi Tracy,
>
>VFP will not perform a check during the build if you remove OLEPUBLIC clause.
>
>
>>Believe it or not this is working. However, when building the app or exe, it requires the .tlb file be located in the directory that it will reside in on the client's machine for the build to complete without errors. That would require that every developer who builds an exe from the source code have it installed.
>>
>>Is there anyway around that? If we ignore the error, it will build of course, but com interop doesn't work (of course). Not all customers will have this interface so I am wondering how to isolate it somehow?
>>
>>I think it is due to the events section:
>>
>>DEFINE CLASS TRAPIEvents AS SESSION OLEPUBLIC
>>
>>IMPLEMENTS ITRAPIEvents IN "C:\Program Files\Power\API\POWER.CACHSTANDARDAPI.TLB"
>>
>>etc...
>>
>>Without that specified though the com interop won't work. We had to put the class definition in our main.prg in order for it to work.
.·*´¨)
.·`TCH
(..·*

010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform