D
Dan
Hello,
I am having trouble serializing a typed dataset that has a number of
expression columns. When I attempt to serialize the dataset, the framework
(.NET 1.1) throws a NullRefException. After a little research I've come
across Microsoft KB 818587 (link below), which describes a similar problem
that is encountered when serializing datasets containing row errors.
http://support.microsoft.com/default.aspx?scid=kb;en-us;818587
In the search for a solution, the only workaround I have found is to remove
the expression values from each column prior to serialization at runtime, in
which case it serializes fine. However this isn't such an elegent solution
and it would be rather painful to maintain on a large scale.
I have a feeling the problem I am having and the problem described in 818587
are related, however since there is only a 'supported' patch for 818587 that
is not directly aimed at my problem, I cannot use it. I wonder if anybody
has encountered the problem described in 818387 and has developed a somewhat
elegent workaround, or alternativly if anybody has encountered my problem
and determined that it is related to 818387?
Thanks for any insight.
Kind Regards,
Dan
I am having trouble serializing a typed dataset that has a number of
expression columns. When I attempt to serialize the dataset, the framework
(.NET 1.1) throws a NullRefException. After a little research I've come
across Microsoft KB 818587 (link below), which describes a similar problem
that is encountered when serializing datasets containing row errors.
http://support.microsoft.com/default.aspx?scid=kb;en-us;818587
In the search for a solution, the only workaround I have found is to remove
the expression values from each column prior to serialization at runtime, in
which case it serializes fine. However this isn't such an elegent solution
and it would be rather painful to maintain on a large scale.
I have a feeling the problem I am having and the problem described in 818587
are related, however since there is only a 'supported' patch for 818587 that
is not directly aimed at my problem, I cannot use it. I wonder if anybody
has encountered the problem described in 818387 and has developed a somewhat
elegent workaround, or alternativly if anybody has encountered my problem
and determined that it is related to 818387?
Thanks for any insight.
Kind Regards,
Dan