Third Choice Or create an object (arrayTable) made up of the number and type of arrays that are needed to match the fields of the record. That object would be using standard REALbasic commands to search in the arrays, append and delete elements in that arrays etc.
I do not know anything about the speed issues, but I cannot see that it would be any slower than your choice one and yet be more "organized" when you do such tasks as entering or deleting a record. You could have an object class for the records if you wanted but that class would not have to be an array. It might be useful (clearer) when writing code to have such an entity to hold a single record. arrayTable.append (value1, value 2 ...) this method would just be array1.append(value1) array2.append(value2) Return Other similar methods can be created to match the usual operations on a single array. On Apr 10, 2007, at 2:50 PM, realbasic-nug- [EMAIL PROTECTED] wrote: > There's a choice as to EITHER have separate arrays for > each field (each array containing the given field for all the > records) OR create an object class for the records which holds all > the fields and make an array for those records (the object instances). _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
