Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Am I forced to use Dot Net?
Message
 
À
26/08/2004 19:14:56
Information générale
Forum:
Visual FoxPro
Catégorie:
Visual FoxPro et .NET
Divers
Thread ID:
00935927
Message ID:
00936828
Vues:
37
I believe there are also several examples listed at the bottom of what I posted where it says See also Solutions Samples
>
>There is a similar example in the VFP documentation. This is the same way you call any COM object, including one that is a wrapper around a .NET class for interop. As I stated before, details about how to apply these product functions like how to build a solution around them will be found in whitepapers and samples on msdn.com.

>>You mentioned something like "VB automating MSWord" being more appropriate in MSDN and not in the help docs - here's what I found in VFP 7 Help Docs(I have a feeling there are a lot of similar examples to refute your statement):
>>Automate a Microsoft Word Document in a Form
>>File: ...\Samples\Solution\OLE\Oleword.scx
>>This sample shows how you can automate an embedded Word object on a form, insert some rich text, and then format the text. Typical automation with Word is usually done using the "Word.Basic" object used interactively with a CREATEOBJECT( ) function.
>>oForm = THISFORM
>>oForm.AddObject('oWordDoc','OleControl','WordDocument')
>>oForm.oWordDoc.Visible = .t.
>>oForm.oWordDoc.DoVerb(0)
>>See Also
>>Automate a Microsoft Excel Spreadsheet | Automate Microsoft Word and Excel | Solutions Samples
>
>There is a similar example in the VFP documentation. This is the same way you call any COM object, including one that is a wrapper around a .NET class for interop. As I stated before, details about how to apply these product functions like how to build a solution around them will be found in whitepapers and samples on msdn.com.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform