Hi Georgi,

I have tried to work with the link that you sent, but without success.  Because I need to move ahead with the project, I am going to try a different approach, displaying null values as zero on the screen and then storing them as null in the database.  The users may not go for it, and if not, then I will have to go back to the drawing board.  So, I wouldn't consider this question answered, but I am dropping the question indefinitely.

Regards,

Ross

Hi Georgi,

Thank you for asking.  I hope to work on this by the end of this week.

Regards,

Ross

Yes, thank you for waiting.  I need a few days to get to this because of some other things that have come up.

Thank you for the link.  It looks like it may be helpful, but I will need some time to try it out.  I will keep you posted.

Regards,

Ross

While your answer has the virtue of being obvious, it is not helpful.  Can you do any better?  You are basically saying that the Infragistics grid doesn't handle nulls fully the way it should.  I can back that up with the fact I have tried this same exercise with other grids, and they work fine.

As a possible work-around, I am going to explore having the grid display all zero values as blank.  If you have anything to suggest on how to best make that work, that will be appreciated.  While it isn't a very satisfying answer, I have to get the job done, and it is too late to switch off the Infragistics grids right now.

Hi Georgi,

Thank you for your quick reply.  I put together a test project that reproduces this problem.  I couldn't attach the whole project because the default IG styles and graphics were loaded into it, so I just zipped up my code files.

Regards,

Ross