>I don't mind the cursors and I usually associate the cursor with the name of the combo (or other control) that is the source for. The naming is protected in that way as I don't have the same names throughout my forms.
>
>To each his own.

I agree with your points & perspective (generally pro-cursor), and I would just add that cursors are considerably more flexible than arrays, by having most of the properties of tables, offering indexing, SQL, and most other x-base table commands. Being able to name columns (cursors) instead of refer to them by number (arrays) is an additional (though mostly cosmetic) nicety. Easier to work with in debugging...

Since we are a datacentric, table-based tool here in vfp, IMO it really makes more philosophical sense to use the method your dev tool excels at. In C, this is arrays. In vfp, this is cursors.

Not a hard & fast rule, as you say - but if one finds oneself unsure of which to employ in any given situation in vfp, I would give the cursor the nod.