Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
ODBC converts null dates to empty dates.
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Divers
Thread ID:
00898995
Message ID:
00899940
Vues:
15
>Hello everybody,
>
>I'm using VFP8 SP1 and SQL 2000 in the back end, there is one field in
>one of the tables that keeps coming back "empty" when in the back end is
>NULL, this causes a conflict; error 1585; when the record is saved.
>I can't figure out what the problem is, any thoughts on that?
>
>I'm using remote views with ODBC
>
>THIS.Thankx("In Advanve")

Are you sure it is the empty date field that is causing the error? Normally, empty date values in VFP get stored into SQL Server as "01/01/1900". Unless your table has a trigger that blocks dates with that value, I'd be surprised that it would cause an error.
Dan LeClair
www.cyberwombat.com
SET RANT ON - The Wombat Blog

Life isn’t a morality contest and purity makes a poor shield. - J. Peter Mulhern
Disclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform