David,

An update on using arrays as RowSourceTypes. I modified my combobox class to use either a VFP table or an array for a RowSourceType. The lookup object creates a table with a SQL select of localized data rather than an array property of the combobox. The combobox opens the table in its data session and deletes the table when destroyed. I tested two versions of the same application. One version uses arrays for all combobox RowSourceType and other version uses VFP tables for RowSourceTypes. Opening three order-entry forms in each application - a total of 60 comboboxes with 4 to 22,500 records. The 22,500 record combobox had to be truncated due to the array bug in VFP 8.0. According to SYS(1016) the array version used about 8.5 meg more memory - 31,629,468 to 23,181,128. But, the big benefit of the array version is SPEED - it loads much faster. I'll stick with the VFP table version but thought I'd ask the question. With todays hardware what's more important - application speed or memory use?

Still waiting for SP1 but VFP 8.0 rocks! I'll never go back!

>Will,
>
>>You're right, I would have rather used a cursor as a RowSourceType and really wanted to. My problem was the cursor must be in the same data session as the combobox. Here's the scenanio.
>
>For all the good they are, private DS's can be a real PITA sometimes. Let your localized versions exist as cursors in the default DS (or as local tables in the temp folder). Then your cbo could do a USE (this.cCursor) in 0 again to get the cursor opened inside the form DS.
>
>>I don't agree with you here. My class works fine using RowSourceType=Array with little perform issues up to 6500 records and 5 columns in a dropdown. The computers are two and three year old P4s with 265 memory.
>
>Wait a minute, I demand strict adherence to my opinion on matters such as these. *LOL*