JHughes
Thu Mar 03 21:35:02 CST 2005
Aido
I am having exactly the same problems with an expression column in a
master-detail related dataset. As you also tried, removing the expression
columns prior to update avoids the error but raises more issues with
databindings.
Did you get around this problem somehow? If so I'd be really interested to
know what you did?
TIA for any help
Jeremy
"aido" wrote:
> Hi all,
> I have made some progress, namely altering my Parent() expressions so that
> they do not refer to columns in parent tables that are themselves
> expressions. This allows me to delete the expression columns from the
> tables prior to update and add then re-add them after the update from a
> collection object. It seems to work but results in other side effects; some
> data bound controls/binding collections get confused and lose connection to
> the data. I can't believe that this is the only solution, it is a complete
> hack, there must be a better way...
> Aido.
>
> "aido" <acreegan@hotmail.com> wrote in message
> news:OXRk5LjpEHA.2900@TK2MSFTNGP12.phx.gbl...
> > Hello All.
> > I am using a strongly typed data set in a C# application. Some of the
> > tables contain columns that are computed values by means of the Expression
> > attribute in the data schema. I get the above exception on an update via
> > the data adapter. I have seen some references to this problem as a known
> > bug with work arounds but none seem to work (I have tried erasing the
> > expression, doing update then re-adding expression and also deleting the
> > column doing update and re-adding it to the table after execution with
> > little success). Please note that some columns are referenced via
> Parent()
> > expressions in child tables. My question is this, Is there a recommended
> > work around for this issue (if it is indeed an issue)?
> > Thanking you all in advance
> > Aido.
> > (Extremely disillusioned .NET hacker).
> >
> >
>
>
>