Webinar 231

Title: A Wrinkle In Time

Date: October 11 2013
Clarion Date:
Duration: A little bit under two hours

Download Recording

Hosts: Arnold Young, John Hickey, Lisa Daugherty, Mike Hanson

Presenter: Mike Hanson

Recently SV fixed the longstanding bug that causes times stored using the TIME field to be properly converted. It was a problem, because when you store your values using the TIME data type, you could _never_ enter a value of midnight. Even though it would save it properly to the database, when it brought it back, it discarded the midnight value.

Now instead, it converts a midnight TIME value (0) to a Clarion midnight value (1). This is good, because it means no more lost midnight values.

Unfortunately, it means that if you're using a TIME field in your database, then you can never represent the value of "No time". All those "b" pictures (like @T4b and @T7b) will go from showing blank to showing midnight. This is a byproduct of Btrieve TIME fields, not a fault of Clarion.

It would be good if Clarion could spot a "Null" datetime in a SQL database, and convert that to Date=0, Time=0, but that still won't work if you're storing your data in Btrieve, which doesn't have a "Null" concept for DATE and TIME fields.

The real problem is that Clarion considers midnight as 1, rather than 0. I'm sure it seemed a good idea at the time, but now that the rest of the world uses 0-offset time, it's become an ongoing challenge.

In this webinar we'll discuss this new behavior and implications. We'll offer different ways of handling it, in both hand-coded source, maybe a function to auto-fix values, and perhaps a template to do it with triggers.


Old Business: None

New Business: None


Topics Covered:

Additional Downloads: None

Slide Show:

Time Events:

Webinar Introduction

Webinar Recording

Fourth Rule Of The Webinar:


comments powered by Disqus