Greg Robinson's Blog

I think I have discoverd a bug when setting the DefaultValue property on DataColumn and serializing a DataSet. 

I have not blogged here in a while, nor have I blogged on my personal site.  Why, two-fold.  One, I just hired a .net developer and I have been very busy with ramp up and training.  Hopefully, he will be blogging here soon, Bill Sanders.

This blog entry got me thinking

I spent last week developing our data management layer.  Most of my testing was done with the CommandBuilder.  Although it is a handy type, I found some limitations, so I developed our own custom model.  I wish Bill's article would have come out a week sooner:

I found myself databinding each control on my form one by one.  To much time, too much work.  Instead, I did this:

I needed a type that could handle an array of strings who's size I never knew.  The StringCollection type handles this very well and has some handy methods for looking into the collection.

It took me a while to figure this one out, but I got it.  I now have a piece of code that allows me to databind a dataset to controls on a client.  The client can then modify the dataset and the changes are persisted back to the datasource without using any config files or external files to describe the stored procedure being used (required paramters, param types, values, etc.).