Hi Geoff

For some reason I've never used NOTIME I usually struggle each time ;-)

Anyway - just tried it. Now I get the /04/2407 date formating so I have had
to put in an edit mask to fix it.

In summary the steps have been
Set the column to NOTIME
Set the display format to dd/mm/yy
Set the edit mask to ::EM::!99!/!99!/!9999;0;_;0

Then it works perfectly :-)
(except for the other focus problem ;-)

Paul

> > I'm using dialect 1 so fields defined as DATE act as (or IBO
> > interprets as) TIMESTAMP :-/
>
> I believe you can use the:
> NOTIME
> column attribute for domain or field names, as a way to tell
> IBO that certain domains or field names have no time (and are
> therefore DateOnly fields). This I believe is both the
> easiest and BEST way to resolve your problem. (It has been
> in IBO for a long time as a way to work around the
> limitations of dialect 1 date types.)
>
> Using that column attribute tells various parts of IBO (and
> my Enh code) that a column is a date only - and so stops it
> attempt to deal with the time.
>
>
> Your alternative is to edit Telesis_IB_DateTimeEnh.pas and
> find: procedure TIB_CustomDateTimeEnh.SysStateChanged;
>
> You should see in there the code that adapts the DateOptions
> according to the data type and string. Comment out that code
> and I think all should return to as it was (just watch out to
> resync your changes when you get updates... not that they are
> happening very often these days).
>
> I am reluctant to remove the specialisation in Enh, because
> that would make the automation unavailable to those that do
> tell IBO whether a dialect 1 DATE field is date only.
>
> --
> Geoff Worboys
> Telesis Computing