DataSet Losing Data when Column Name Contains Colon

Hi,

Somebody else has posted something in regards to this before, but that
was back in 2002. You can see his post at:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=0f0c01c233f2%24988a7c30%24a4e62ecf%40tkmsftngxa06&rnum=4&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26q%3Ddataset%2Bcolon%2B.net

Microsoft has also made mention of this same problem. You can see
Microsoft's FIX at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;818962

The FIX was posted in late 2003, but I have not seen any resolution to
the problem. The problem must still exist since I am experiencing it
today (2004).

So, my problem is this:

I have a dataset that gets populated by calling multiple stored
procedures. The dataset is successfully populated. The stored
procedure returns column names that contain colons (":"). When I do
WriteXml(fileName, WriteSchema), I the dataset is saved successfully.
When I load the file back, using ReadXml(fileName, ReadSchema), the
dataset (its datatables, rather) have appropriate structures. The
problem, though, is that the datatables that have column names that
contain colons, result in the column being completely populated with
DBNULL. I need help finding a work around to this. Any help is
greatly appreciated. Keep in mind that I cannot change the stored
procedure (in order to return appropriate column names).

I hope I was clear as to what my problem is.

Again, any help is greatly appreciated.

Regards.
Jacques

edwardmur
Mon Sep 13 13:49:14 CDT 2004

Sorry, I don't have a solution to this - just the same problem as you! Just
wondering if you ever found a solution...

Ed.

"Jacques" wrote:

> Hi,
>
> Somebody else has posted something in regards to this before, but that
> was back in 2002. You can see his post at:
>
> http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=0f0c01c233f2%24988a7c30%24a4e62ecf%40tkmsftngxa06&rnum=4&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26q%3Ddataset%2Bcolon%2B.net
>
> Microsoft has also made mention of this same problem. You can see
> Microsoft's FIX at:
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;818962
>
> The FIX was posted in late 2003, but I have not seen any resolution to
> the problem. The problem must still exist since I am experiencing it
> today (2004).
>
> So, my problem is this:
>
> I have a dataset that gets populated by calling multiple stored
> procedures. The dataset is successfully populated. The stored
> procedure returns column names that contain colons (":"). When I do
> WriteXml(fileName, WriteSchema), I the dataset is saved successfully.
> When I load the file back, using ReadXml(fileName, ReadSchema), the
> dataset (its datatables, rather) have appropriate structures. The
> problem, though, is that the datatables that have column names that
> contain colons, result in the column being completely populated with
> DBNULL. I need help finding a work around to this. Any help is
> greatly appreciated. Keep in mind that I cannot change the stored
> procedure (in order to return appropriate column names).
>
> I hope I was clear as to what my problem is.
>
> Again, any help is greatly appreciated.
>
> Regards.
> Jacques
>

googlegroup6a
Wed Sep 22 11:08:51 CDT 2004

Hi,

I appreciate the response. I have not came upon a solution yet.
Currently I am just using an ugly hack waiting for a solution. I am,
sadly enough, just removing the colons from the column name. There
are probably other characters that cause the problem, but I'm unaware
of them. Microsoft should've fixed this by now since they know about
it.

Thanks again.

edwardmur <edwardmur@discussions.microsoft.com> wrote in message news:<CB760BDC-233A-490F-A7F2-DC50D5EA1AE2@microsoft.com>...
> OOPS
>
> Apologies,
> Ignore that last post - the workaround doesn't work! - I got so excited that
> I wasn't getting error messages anymore that I posted it without having
> tested it properly - hope I didn't waste your time. I have worked out a way
> that does work now (really!) and tested it properly :)
> Its not very elegant but you can just rename the columns in the dataset
> before writing the xml, and before reading it - then just change them back
> once the data is loaded - e.g, for a column called "Name:" in a table called
> "Table"
>
> dataset.table._name_column.columnname="Name"
> 'then write your xml
> 'then if you need to, change it back
> dataset.table._name_column.columnname="Name:"
>
> and to read:
>
> dataset.table._name_column.columnname="Name"
> 'then read your xml
> 'then change it back
> dataset.table._name_column.columnname="Name:"
>
> Hope this one does help, apologies again for the last post :)
>
> Ed
>
> "Jacques" wrote:
>
> > Hi,
> >
> > Somebody else has posted something in regards to this before, but that
> > was back in 2002. You can see his post at:
> >
> > http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=0f0c01c233f2%24988a7c30%24a4e62ecf%40tkmsftngxa06&rnum=4&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26q%3Ddataset%2Bcolon%2B.net
> >
> > Microsoft has also made mention of this same problem. You can see
> > Microsoft's FIX at:
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;818962
> >
> > The FIX was posted in late 2003, but I have not seen any resolution to
> > the problem. The problem must still exist since I am experiencing it
> > today (2004).
> >
> > So, my problem is this:
> >
> > I have a dataset that gets populated by calling multiple stored
> > procedures. The dataset is successfully populated. The stored
> > procedure returns column names that contain colons (":"). When I do
> > WriteXml(fileName, WriteSchema), I the dataset is saved successfully.
> > When I load the file back, using ReadXml(fileName, ReadSchema), the
> > dataset (its datatables, rather) have appropriate structures. The
> > problem, though, is that the datatables that have column names that
> > contain colons, result in the column being completely populated with
> > DBNULL. I need help finding a work around to this. Any help is
> > greatly appreciated. Keep in mind that I cannot change the stored
> > procedure (in order to return appropriate column names).
> >
> > I hope I was clear as to what my problem is.
> >
> > Again, any help is greatly appreciated.
> >
> > Regards.
> > Jacques
> >