For a MS definition, just use VBHelp, Index tab and type in VBNullstring. According to them it should only be used for calling external procedures.
________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first
'If we're supposed to work in Hex, why have we only got A fingers?'
A "" is nothing, where as a vbnullstring is actually a chr(0). The difference is a byte of data, which is not a lot in normal circumstances. If you want to join an array of 1000 bytes, and you use a null string, the string will be 2000 characters, where as if you use "" the string will be 1000 characters.
BB
Could you point me to the reference that gives vbNullString as Chr(0), as that is not my understanding of it.
vbNullChar is Chr(0)
________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first
'If we're supposed to work in Hex, why have we only got A fingers?'
vbNullString - String having value 0 Not the same as a zero-length string ("" used for calling external procedures
In VB an equal test between vbnullstring and "" returns true. Would I be right then in saying that a vbnullstring is a zero length string ("" with a null terminator (vbNullChar) which VB does not need but some external procs do eg APIs.
what i'm writing about is the fact that what the goal is, is to yield a record that looks like this when the value of the AE_Attribution_Code variable is null (i.e. when the data entry people don't enter anything into the column for it)
someone's suggested using vbNullString but i tend to think it's not any different that entering "" in the same part of the code. is there something that would have the effect of exporting 'nothing' to the export file?
“The philosophy of the school room in one generation will be the philosophy of government in the next." --- Abraham Lincoln
You'll probably find that "" and vbNullString differ a bit in the data that is actually contained in the header.
Remember vb is a size prefixed string.
I could see if you looked at the the actual memory map that BSTR header for a vbnullstring would have a 0 size while "" would have a size of 1 because it is actually null terminated. Or vise versa.
Hope I've been helpful,
Wayne Francis
If you want to get the best response to a question, please check out FAQ222-2244 first
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.