@Ross, yeah, it's still pretty much the same thing, though. My point was that if you look at your data in terms of database terminology (i.e. in a table), arrays are suited for referencing the individual schema (columns), and custom types are suited for referencing the individual records (rows). (Though I wrote the table sideways in this case because it was easier, so the schema are rows and the records are columns.)
Also, in general, it should be noted that when you create custom types, a linked list of each instance is created for you. There are distinct advantages (and disadvatages) to this which I won't get into. Just do a search on "linked list" versus "array" data structures. (Also, note that some people like to have the "best" of both worlds by putting their linked list elements *into* an array...)
@Pete, er... are you sure you meant that for me?
Also, in general, it should be noted that when you create custom types, a linked list of each instance is created for you. There are distinct advantages (and disadvatages) to this which I won't get into. Just do a search on "linked list" versus "array" data structures. (Also, note that some people like to have the "best" of both worlds by putting their linked list elements *into* an array...)
@Pete, er... are you sure you meant that for me?