>.BoundColumn takes on a numeric argument, not needed in this case, coz'

Yes it is a numeric value, didn't mean to imply otherwise. As for not needing it, that depends on whether you want to display different information in your combo than you want to use for processing purposes.

As an example;

TASKCLAS_ID is an integer type column used to identify task types (classes) within our task management system. This numeric identifier is used throughout the application for a couple of reasons. Integers take up less space than character types, and integers are much easier to automatically increment, and to use as parameters in views/queries/etc...

TERSELISTING is a C15 that contains a short description of the task class.

In the grid, the combo displays the terselisting when dropped down. However, the value stored in the table is the taskclas_id.

>.RowSource is single field. Shouldn't RowSource read "curCatTypes.Cat_ID" ?

The rowsource property contains the name of the cursor/array/ ... containing the data for the combo, it does not contain a specific reference to the columns.

A large portion of the reasoning behind this methodology is to 1) NOT duplicate engine behavior, and 2) less is more in terms of less code = improved / faster functionality. A certain amount of code is going to be necessary, but a concerted effort to reduce the amount of code, and call on engine behavior whenever at all possible almost always improves the overall product in terms of speed and reliability. I can't speak for your users, but mine will always sacrifice a bit of speed for reliability.

This is not the only way to do what you are after. It is the prefered methodology of my development team. This methodology always works, and is lightning fast with very little code.

Regards,

Jason