RE: Date entry

2018-07-05 Thread Timothy Penner via 4D_Tech
> 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

Re: Date entry

2018-07-05 Thread Jody Bevan via 4D_Tech
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 t

Re: Date entry

2018-07-05 Thread Pat Bensky via 4D_Tech
Thanks Jody - yes I can follow all that, no problem :) Sounds like a fair bit of work though, which I would prefer to avoid ... PB On Thu, 5 Jul 2018 at 15:37, Jody Bevan via 4D_Tech <4d_tech@lists.4d.com> wrote: > Pat: > > In Canada every possible date format was used by different clients. > Th

Re: Date entry

2018-07-05 Thread Jody Bevan via 4D_Tech
Pat: In Canada every possible date format was used by different clients. Therefore we had to write our own date handler. Essentially we handle it this way: 1. We let the system administrator set the format for all dates to be displayed. This includes all the ways 4D has built in way, but also i

Re: Date entry

2018-07-05 Thread Chip Scheide via 4D_Tech
I am not using anything near v16... but have you tried to explicitly set the display format for the date areas during On Load, using code? set object format(*"object_name";Date_format) On Thu, 5 Jul 2018 12:43:55 +0100, Pat Bensky via 4D_Tech wrote: > Thanks Wayne. > I'm using v16r6 and it won't

Re: Date entry

2018-07-05 Thread Pat Bensky via 4D_Tech
Thanks Wayne. I'm using v16r6 and it won't let me revert to 16.3. I don't think v17 is ready for prime time yet ... Grrr! So, anybody got a suggestion for a workaround? PB On Thu, 5 Jul 2018 at 12:23, Wayne Stewart via 4D_Tech <4d_tech@lists.4d.com> wrote: > Pat, > > There’s a 4D bug regarding d

Re: Date entry

2018-07-05 Thread Wayne Stewart via 4D_Tech
Pat, There’s a 4D bug regarding dates. What version of v16 are you using? The latest nightly builds of v16 dot releases should be fine. If you’re using 16r something, then it’s fixed in v17. Wayne On Thu, 5 Jul 2018 at 20:50, Pat Bensky via 4D_Tech <4d_tech@lists.4d.com> wrote: > Jody, > I'm

Re: Date entry

2018-07-05 Thread Pat Bensky via 4D_Tech
Jody, I'm using v16 and having the following problem with date formats: On a UK system, dates in fields and list boxes are incorrectly displayed in 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 Bev

Re: Date entry

2018-06-11 Thread Robert McKeever via 4D_Tech
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 tool for the date > entry, and display

Re: Date entry

2018-06-10 Thread Jody Bevan via 4D_Tech
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 are. The for