[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Brett Callacher
Sent: Friday, 12 November 2010 6:16 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Val on UniDynArray produces unexpected results
I think you will find that the problem here is two expressions, on the same
line
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Brett Callacher
Sent: Friday, 12 November 2010 6:16 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Val on UniDynArray produces unexpected results
I think you will find that the problem here is two expressions, on the same
line
var1.Field(1).StringValue
Do you mean that? Or do you mean var1.Field(1).StringValue ?
Differences between the P-Code and fully compiled code have been a 'feature'
of VB for a long time - the compiled code is generally more accurate/less
forgiving and - whilst not relevant here - if you have
What are you expecting when doing a operator on a string ? I am not sure
what the result should be in that case ??
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Adrian Halid
Sent: 12 November 2010 02:18
To: u2-users@listserver.u2ug.org
Adrian Halid adrian.ha...@itvision.com.au wrote in message
news:13e4ae055d203648a4121114f2458c8c9f16a05...@tefnut.perth.itvision.com.au...
Hi All,
We have come across a very strange bug between UniDynArray and VB6.
In our applications we were getting two different results on an if
Testing a string is a valid way to test for a non-null variable IMO. If
you think about it a string can never be . Am not aware of a language,
p-code or otherwise, where that is not the case.
Brett
Brian Leach br...@brianleach.co.uk wrote in message
