>I have an Access database and I use remote views to get to it. For some reason, fields that are null in Access sometimes come across null in Fox and sometimes come across as blank. If the field comes across as null or with some information in it then I can change it when I browse the view. If it comes across as blank (empty for text fields, / / for date fields) then me trying to put something in there causes an "update conflict".
>
>It's not like it's differences in the field settings because I'm talking about the same field (although it appears to happen with all of them, so it's not like the problem is contained to a particular data type). For instance, I have a field called first_name. If the Access table has null for first_name, then it could either come across as null or as blank/empty. If it comes across as null, then I can put information in there and go to another record, no problem. However, if it comes across blank/empty, then when I try to put information in there and go to another record I get the "update conflict" error message.
>
>Anyone have any idea why sometimes the null fields come across as null and sometimes they don't? Anyone have any idea how I can make sure they come across as null? Thanks!

What if you change the update type to Key Field Only?