Hi,
I had the same problem and the following helped:
place SET ANSI_NULLS OFF right in front of your update command. That 
will make the comparison between the NULL value hold in the original 
value of the gridview control and the one found in the table work as 
it should during the update. Check SQL Help for a detailed 
explantion why this is the case.

Regards
 

--- In [email protected], "azenhi" <[EMAIL PROTECTED]> wrote:
>
> 
> 
> This should be simple, but I cannot find a mention of it anywhere:
> 
> Using webdev Express, I've created a single page with an 
> AccessDataSource and GridView. It selects one table from Access 
and 
> displays. Very simple, just the basics.
> 
> I used the wizard to auto-generate the Update/Insert/Delete 
commands 
> and editing/updating the GridView works fine . . . . again, this 
is 
> just following the instructions in the help file, no changes to 
any 
> of the autogenerated stuff.
> 
> Editing and Updating works --- UNLESS a field in the original 
table 
> was blank or is made blank through editing. If any cell is blank 
> (null) then the update fails - nothing happens, the page just 
> refreshs to non-edit mode. The data is not updated in Access 
either.
> 
> I have also tried and had the same results with SqlDataSource.
> 
> The key here is the table has a "File_Note" column - and there may 
> be no text in the filed for any given row, it will be blank or 
null.
> 
> What am I missing? Do I need to check for nulls on the RowUpdated? 
> and then set them to what? Null?
> 
> For simplicity the table has three columns: 
> "File_ID" (auto-increment/PrimaryKey)
> "File_Name" (Text, AllowNulls - yes)
> "File_Note" (Text, AllowNulls - yes)
> 
> Let me know if you need more info, any help appreciated
>









 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/AspNet2/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to