Another way is to replace the field in the remote view before tableupdating the new record. I guess remote views are not smart enough to query the back end to get default values. I can't believe that I'm the only one to have this problem!


>Ok, whats happening is that after inserting a new record in the remote view and tableupdate(), the date field is getting set to an empty date in the remote view instead of a null. Anybody know how to fix this (other than doing a REQUERY every time I insert) ?
>
>
>
>>I have a remote view going against SQL server. If I try to update a record that had a null date field with a non-null date, I get an update conflict. This is because the remote view is sending a SQL command that looks like this:
>>

>>UPDATE ordercomments set tedited = 'Apr 29 2002 11:44AM' where uordcommid=1 and teditedon=SPACE(23)
>>

>>
>>The problem is the teditedon=SPACE(23) condition will never find my null date. How can I tell the remote view to send
>>

>>teditedon is null
>>

>>
>>instead?
>>
>>TIA