>>>Not necessarily. 7 is the default behavior for all windows combos and if that standard changes then 0 will, theoretically, show the new default. 7, on the other hand , is specifically 7 items regardless of any underlying default count.
>>
>>Valid point, gentlemen. I guess I'd like to see a little more standardization in these properties, though...e.g., defaults like: combo columncount = 0 (why not 1?), grid columncount = -1 (why not 1?)...
>
>The combo I don't know why, but the grid there is a difference between -1 and 1. 1 gives you one column, while -1 gives a column for every field in the recordsource at runtime.

You're right, but then why not use 0 for grid.columncount then to be more consistent, since there doesn't seem to be any reason to ever use the 0 setting for? Then at least there'd be a standard of sorts...