Dataset wierdness

Hopefully this is the correct forum...

I have a large dataset with about 20 tables. This morning I added a new column to one of these tables - called Note. It's a text field. I updated the stored proc that selects/updates the table, remapped the columns in the dataadapter, updated the client to set values in this, tested it and it worked fine.

Then I checked everything in and started to add a whole new table.

Suddenly I started getting a problem with my new Note column. If I call IsNoteNull() I get an invalid column, ie: it's null. If I drill into the dataset reference code, I can see that InitClass() correctly adds the columns to base, but in InitVars() the column no longer exists in the base.Columns collection - yet all the other columns do.

I've tried renaming the column. I've tried deleting and readding the column. I've checked that the column is defined correctly in the dataset. Nothing seems to help.

Has anyone ever seen anything like this before?

I'm using VS05 B2 and SQL 2k. The dataset is returned from a web service to a winforms client.

[1081 byte] By [Jonesie] at [2007-12-16]

.NET Development

Site Classified