Hi Dave,
If you were not planning on using a database then you could use a
hash table to store the Vx values and fetch the corresponding unique
number from the dictionary. You could then use this to look up the
rest of the data using a second hash table.
REALbasic has a dictionary class implements a hash table as a fast
lookup. It should work okay for you.
If not just search for "hash table" on the web and you will find more
than enough information to build your own.
Good luck with it.
Cheers,
Malcolm
On Aug 30, 2007, at 6:16 PM, Dave Shirk wrote:
> Malcom,
>
> Thanks for the suggestion. A database is still an option,
> but I am not convinced this is the most efficient, but it very
> well might be.
>
> I guess the fact that there are about 350 Unique Number entries,
> but well over 3,000 "Vx" values, it seems cumbersome.
>
> But as I said, perhaps your database suggestion is the best
> solution.
>
> Dave Shirk
> Oriental, NC
>
>
> On Aug 30, 2007, at 5:15 PM, Malcolm Smith wrote:
>
>> I assume that you are storing this data in a database.
>>
>> You could create a table that contained Unique Number and one Vx
>> value.
>>
>> Your main table would have Unique Number, Unique ID String, etc. but
>> not the Vx values.
>>
>> When you want the Vx values for a given record you just do a join to
>> pull out the ones with the matching Unique Number.
>>
>> Cheers,
>> Malcolm
>
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
>
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|