VB vs VBscript type diferences

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

everymn@yahoo.com - 22 Feb 2007 02:25 GMT

Hi,

I'm trying to narrow down whether we have a problem in our ODBC
drivers. One test script that checks field type is returning
different values between VB6 and VBscript. Does anyone know whether
this behavior is common? Is the does it gauge the difference between
var, and longVar based on defined size? The seems likely to me
because the defined sizes of these fields are also different between
the two environments.

Thank You

adLongVarChar in VB6 is becoming adVarChar in VBS
adLongVarBinary in VB6 is becoming adVarBinary in VBS

Reply to this Message

Ralph - 22 Feb 2007 12:46 GMT

> Hi,
>
[quoted text clipped - 10 lines]
> adLongVarChar in VB6 is becoming adVarChar in VBS
> adLongVarBinary in VB6 is becoming adVarBinary in VBS

The short answer is that these defined data types don't exist in either
language. They are only a property of the data access library being used and
the provider's best guess from what the engine is telling it.

Need to know more about the specifics. It might help to appreciate that VB
and VBS are totally separate languages with separate VMs.

hth
-ralph

Reply to this Message

Ralph - 22 Feb 2007 14:23 GMT

ie, Look not in the bowels of the languages, but in the versions of ADO and
Providers you are using.

Also, check the actual 'value' against whatever 'const define mapping' is in
use in the environment you are testing. It is just possible that adVarChar
does equal adLongVarChar.

-ralph

Reply to this Message

VB Forum / Database Access / February 2007

VB vs VBscript type diferences