On Mon, 23 Feb 2004 16:52:20 -0000, "Steve" <stevea@centurion-ms_RemoveThis_.co.uk> wrote:

"Paul Clement" <UseAdddressAtEndofMessage@swspectrum.com> wrote in message
news:5atm30p0cgo3k14a042oe6kvebssp8sbng@4ax.com...
> On Mon, 23 Feb 2004 16:52:20 -0000, "Steve"
<stevea@centurion-ms_RemoveThis_.co.uk> wrote:
>
> ¤ Hiya
> ¤
> ¤ I have a strongly-typed DataSet that I am using in my form. The ID's for
the
> ¤ tables in the dataset are of an Int data type and are the Primary Keys.
They
> ¤ are automatically generated by the server when the record is saved. When
I
> ¤ add a new record to the dataset I get an error 'Column UserID does not
allow
> ¤ nulls'. In the xsd for the dataset I have looked at the column and it
has a
> ¤ check in the Nullable checkbox.
> ¤
> ¤ Is there a way to ignore the value of this field? It will always be null
for
> ¤ new records because the database inserts the correct value when saved.
>
> If I had to take a guess I would say that allowing a null value for the
UserID column is violating a
> primary key constraint for the strongly-typed DataSet.
>
>
> Paul ~~~ pclement@ameritech.net
> Microsoft MVP (Visual Basic)

On Wed, 25 Feb 2004 19:15:40 -0000, "Steve Amey" <steveamey@hotmail.com> wrote:

"Paul Clement" <UseAdddressAtEndofMessage@swspectrum.com> wrote in message
news:a4bv30tumi6d7turjd4fsnc4nfkkpan25d@4ax.com...
> On Wed, 25 Feb 2004 19:15:40 -0000, "Steve Amey" <steveamey@hotmail.com>
wrote:
>
> ¤ Hi Paul
> ¤
> ¤ Thanks for your response. Have you used or do you know any-one who uses
> ¤ Strongly-typed datasets and how they avoided this problem? I made the
> ¤ database field an IDENTITY type so I wouldn't have to worry about
populating
> ¤ the ID field with a value (amongst other things!).
> ¤
>
> Since the value is auto generated anyway, can't you just plug a constant
value in to work around the
> xsd issue?
>
>
> Paul ~~~ pclement@ameritech.net
> Microsoft MVP (Visual Basic)