>>I was more interested in why you prefer a cursor as opposed to a table.
>
>In this particular case I was thinking you may have fields in different order in the table. With selecting records into the cursor you can select fields you want to show in the combobox the way you want. If you use the table directly then the first N fields will show in the combobox, where N is the columncount.
>
>Or is that what you mean when you say Alias? I thought alias was simply a nickname for any table, cursor etc. Maybe things have changed since my FPW days?
>>
>
>Yes, alias is a nickname for a table or cursor and that's why I suggested to try with Alias as a RowSource.
>
>>Hmmm, is it possible that a RowSource of "2 - Alias" might be more forgiving in the user's runtime environment? I'm wondering how my VFP appl will find tables, defined in the data environment, if they are located on different drives that in my development environment?
>
>As long as your SET PATH correctly pointing to the production database folder and not the development's DBF folder, it should work.

As for using a cursor or table as the RowSource for my combo, I am only trying to display a list of item codes and item descriptions. If I use a table (as opposed to a cursor), I can still control the order of the fields displayed in my combo's list using depending the RowSource property. e.g. RowSource=Lookup.field1, field2 vs RowSource=Lookup.field2,field1. Maybe I'm not understanding something ? - which is happening a lot as I learn VFP :)