In Digital Awakening's original post, he said that it worked when he uncommented the line that set the string to "".
When the line that sets the string is commented out, he gets the failure. In that case his test array has one testType object.
I don't know how the compiler handles initializing the values in arrays made from UDTs.
When I run Digital Awakenings original code, with the commented line, the error message is:
Quote: "Failed to write string, the string has not been assigned a value at line <x>"
Uncommenting the line makes it work.
And I was wrong about trying it with a simple variable declared as a string, but without assigning a value. You get the same error.
Unlike numbers, where a default of zero works because the memory allocated for the variable will be set to zero, a string is more complex.
Strings in basic are dynamic creatures. The memory allocated will start with the number of characters in the string, followed by the characters themselves. And probably a null character to definitively end the string, but not necessarily.
But you have to set a string value before it knows how much memory it needs to allocate. Effectively, an undefined string is a pointer with a null value.
Cheers,
Ancient Lady
