Information générale
Catégorie:
Codage, syntaxe et commandes
That's what you have to do. Most "real" databases (and Access pretends to be a "real" database) do not accept empty dates. Dates (or datetimes) have a value or they are null.
If the database will not accept null, you must supply a populated date.
This is one place where Foxpro data is fundamentally incompatible with every other database system. VFP is the only place where EMPTY() is a valid value for a date or datetime field.
If you can't pass null, you have to provide a valid date value.
Dan
>I ended up putting in 01/01/1900 just to get my import to work properly; this one problem kept making the import fail.
>
>Thank you Boris,
>
>Cecil
>
>>Unfortunately I have no big experience with remote views.
>>You map a DateTime field to Date one in the view, right?
>>I thing that it is a VFP job to conver it back to datetime when you send back to ACCESS.
>>Not sure about EMPTY DateTime fields in ACCESS also, but maybe in ACCESS that field is not NULLable and when you send back a NULL in that field you got errors. What happens if you put: DATE(1900,1,1) in your RV instead of empty date or NULL?
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement