Hi Naomi,

Sorry late in the chain, but I'll throw-in a few thoughts for you... I have built (over the years), a dynamically built grid, custom columns, sortable headers, etc... Its available in the downloads section at www.pafox.org.

Anyhow, my grid building framework is data driven (header table per grid-- primary alias, sorts, etc, and detail table -- fields, read/only, pixel width, captions, sorts, etc)

I also allow for custom controls to be dynamically added to the grid (via the grid build detail table).

To handle your situation based on the "which field" to show, I would have something like an integer column as a flag for type of information. What I would then do is build a custom "button" class, and in its click event have a test for the value in the record (identifying the type of info), and have that button launch whatever was to be the next step... This way, you would have other internal "key" information on the current record you could use and go from there...

Just a thought.

Don

>>That should work, if you are not doing the entire grid you have to prevent the grid from blowing up with one of the standard techniques. Also this adds the column to the end of the grid so you may need to adjust the column order as well.
>
>Hi Robert,
>
>After discussion with my manager we decided to just hardcode these 2 cases.
>
>However, I have a little problem. I have a method that creates a cursor, which is later used for the grid.
>
>Do you think I should just add an extra field to this CREATE CURSOR command or should I have case statements here as well? I'm not yet sure if FormatType would be already available when this method is fired, thoug I can adjust that.
>
>Thanks.