> I'm using v16r6 and it won't let me revert to 16.3.
Just to clarify, this is likely because object notation has been enabled; which
essentially upgrades the structure file from v16 to v17, making it unable to be
opened in v16 afterwards.
See this image and the warning about it not being able
Pat:
I was a lot of work. Especially going through a large application and changing
it all over. We got forced into it by regulation of supporting different date
formats across different government regulatory regions. So we decided to just
do it the flexible way and provide many more features
a workstation is configured, the date is always
> displayed in a consistent format in our system.
>
> 3. The next nasty issue is date entry. For this we permit two options:
>
> a) The system administrator sets up an entry filter using our
> interface. Nothing fancy, the user must en
no matter how a workstation is configured, the date is always
displayed in a consistent format in our system.
3. The next nasty issue is date entry. For this we permit two options:
a) The system administrator sets up an entry filter using our
interface. Nothing fancy, the user must enter
n
>>> the US format. But when you click into a date field, it changes to the UK
>>> format!
>>>
>>> How do you manage this?
>>>
>>> Pat
>>>
>>> On Sun, 10 Jun 2018 at 15:46, Jody Bevan via 4D_Tech <
>> 4d_tech@lists.4
; format!
> >
> > How do you manage this?
> >
> > Pat
> >
> > On Sun, 10 Jun 2018 at 15:46, Jody Bevan via 4D_Tech <
> 4d_tech@lists.4d.com
> > >
> > wrote:
> >
> > > Bob:
> > >
> > > Nasty date formats.
>
> On Sun, 10 Jun 2018 at 15:46, Jody Bevan via 4D_Tech <4d_tech@lists.4d.com
> >
> wrote:
>
> > Bob:
> >
> > Nasty date formats. About 15 years ago we created our own tool for the
> > date entry, and display in 4D. The dates are always stored in date
>
Bevan via 4D_Tech <4d_tech@lists.4d.com>
wrote:
> Bob:
>
> Nasty date formats. About 15 years ago we created our own tool for the
> date entry, and display in 4D. The dates are always stored in date fields,
> but we let the user define the way the dates get displayed. This way
Well, looks like the form was corrupt. I rebuilt it using one that was similar,
and it now works.
> On Jun 10, 2018, at 7:46 AM, Jody Bevan via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Bob:
>
> Nasty date formats. About 15 years ago we created our own to
Bob:
Nasty date formats. About 15 years ago we created our own tool for the date
entry, and display in 4D. The dates are always stored in date fields, but we
let the user define the way the dates get displayed. This way it does not
matter what the computer’s region or date settings
English keyboard instead of US. So, date entry gets
set to -MM-DD instead of MM-DD-.
Dates display fine, regardless of format. But, on a couple of machines, you can
not enter dates. I take my record, place the cursor in the field, and type - it
moves the cursor along the character string
11 matches
Mail list logo
