Hi again Todd ---
>> Yup. ODBC (I think) cannot handle blank dates well and you're at the mercy of the database engine and/or VFP as to how they are
> defined. Try converting the views date fields to DateTime and set them to allow nulls. When saving a record with a blank date (which Fox
> allows), save a .NULL. instead.
>
>Using datetime fields is worth a shot. I was thinking about trying to convert them all to character fields, and see if my insert command would translate the field type on update. (ie, I would DBSETPROP on my local view to change datatype = C(10) and then stuff a DTOC() value into the field.
>
No no no.......storing them as characters will only make your life miserable *if* it can even be done, which I doubt. Bear in mind what I said about NULLs and you'll muddle through it.
>Any thoughts on using INSERT instead of some fancy SQLEXEC() command?
>
Well....if you can resolve your view definitions to your satisfaction it's zero-sum which will work best for you...I am a firm believer in sticking with either remote views or SQL passthrough and never the two should meet, so to speak.
>Thanks for the reply man! I've been really down about this today.
>
Anytime, bud. Been there, done that, got the cruddy T-shirt :-)
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05