>>Store the value of Framework.DateFunction.GetEmptyDate() to a local variable so it doesn't get fired with every loop. For that matter, you could just say:
>>
>>
>>"SET MitTelLog.XMLDowndt=NULL"
>>
>>
>>and not use the function. SQL doesn't allow empty date values anyway.
>
>Using NULL will return a message saying that the null value is not accepted. This is why the function returns a universal date of 30/12/1899 00:00:00.
OK. I would still store that universal date to a variable so the GetEmptyDate() doesn't fire all of the time.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: 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.
