Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Passing Parameter of array type to COM object
Message
De
12/04/1999 17:01:40
 
 
À
12/04/1999 15:18:39
Information générale
Forum:
Visual FoxPro
Catégorie:
Produits tierce partie
Divers
Thread ID:
00207199
Message ID:
00207583
Vues:
16
I have been poking around somemore and have actually come up with the question I need answered but just don't know how to do it in VFP 6.0. The COM objects on the remote server are written in Java and the ISimpleList Interface is what I am accessing when I refer to lcProgistics.OrderAttribute(ix, "WEIGHT") where ix is the Index(specifies which position of the list you want to retrieve an item from). The documentation says that "Each item in a list must be a Variant which, in turn, can be either of type VariantString or of VariantDispatch which can contain any type of object. The documentation also specifies Property(propget) or VARIANT Item(long index). In the VB5 sample, they define all of their variables as new variant(object).

How do I define my variables as type variant dispatch?

I have been reading through the MSDN library which has an entire section dedicated to the Put and Gets of variant representation but I am not familiar with Java or VB and would like to know which commands would be specific to Fox?

So when I say...
lcProgistics.OrderAttribute(ix, "NO_PACK") = "FALSE" or
lcProgistics.OrderAttribute(ix, "WEIGHT") = "21"
I am getting an invalid function, type, or value because I believe that it is not in the right character type. I ultimately would put the weight and no_pack into variables on my form anyway and was using this as a test but would like to know how to redefine these variables to VariantDispatch or VariantString.

ix = 0 and I believe that lcProgistics.OrderAttribute might be called a java safearray. It is a zero based array. I have added more lines with lcProgistics.OrderAttribute.AddLineItem() and even hard coded the following which also did not work because like I said above, it is a typing difference.
lcProgistics.OrderAttribute(1,"WEIGHT") = "21"

Both VARTYPE() and TYPE() return .NULL. on lcProgistics.OrderAttribute(ix, "WEIGHT") OR 'X'-which is undefined.

Thanx again for sticking with me on this.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform