Thanks Martin. Do you know if Native Code runs slower/faster/the same as
P-Code?
-Original Message-
From: Martin Scholl [mailto:[EMAIL PROTECTED]
Sent: Friday, August 27, 2004 11:24 AM
To: [EMAIL PROTECTED]
Subject: RE: [U2] [ud] UniObjects Dynamic Array Type Mismatch only in
.exe
Have you tried a CInt around the dArray.Value(2,1). I'm guessing that
the dynamic array object stores everything as strings or variants.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Burwell, Edward
Sent: 23 August 2004 17:18
To: '[EMAIL PROTECTED]'
I've gotten into the habit of always specifying the StringValue or TextValue
property with each statement. The UniObjects document states that the
StringValue property is the default property, but I've encountered this
issue too many times too feel comfortable not specifying the property.
10:
Dynamic assignment of array variables may be the issue.
Try adding a line so it reads like this.
10: dArray.Value(1,1) = Some String
40: dArray.Value(2,1) = 50
68: temp = dArray.Value(2,1)
70: dArray.Value(2,1) = temp + 25
* 70: dArray.Value(2,1) = dArray.Value(2,1) + 25
90: iNumber =
Matthews [mailto:[EMAIL PROTECTED]
Sent: Monday, August 23, 2004 1:23 PM
To: [EMAIL PROTECTED]
Subject: RE: [U2] [ud] UniObjects Dynamic Array Type Mismatch only in
.exe
Have you tried a CInt around the dArray.Value(2,1). I'm guessing that
the dynamic array object stores everything as strings
