RE: table/field token

2018-09-05 Thread Timothy Penner via 4D_Tech
> Surely something to do with dot notation, but I wonder if it's a bug or > something I miss? There is a section of the docs that talks about this: http://doc.4d.com/4Dv16R4/4D/16-R4/Using-object-notation-preview.300-3303773.en.html#3304590 { Activating the object notation Over any versions, 4D

table/field token

2018-09-05 Thread Arnaud de Montard via 4D_Tech
Migrating from v14r5 to v16r6, dot notation on. In fomulas referencing fields, I have things like this: TimeStampToText([:2]:3) In v16r6, such token is no longer recognised ; I've found 2 turnarounds : 1/ add the table/field names before the token: TimeStampToText ([aTable:2]aField:3) 2/

RE: v13 - screen redraw

2018-09-05 Thread Stephen J. Orth via 4D_Tech
Chip, Have you tried procedurally changing the size of the window (i.e. 1 pixel wider, then smaller)? Steve -Original Message- From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Chip Scheide via 4D_Tech Sent: Wednesday, September 05, 2018 2:37 PM To: 4D iNug Technical

Re: table/field token

2018-09-05 Thread Richard Wright via 4D_Tech
> * Starting with 4D v16 R4, "." and "[]" characters are no longer allowed in > names of tokenized objects. I take that to mean they are no loner allowed in “new” names of tokenized objects. > Date: Wed, 5 Sep 2018 18:50:28 + > From: Timothy Penner > >> Surely something to do with dot

Re: [v16.3 64 IC on El Capitan] Receive file

2018-09-05 Thread Richard Wright via 4D_Tech
Can you clarify "in fairness, it is legacy software, free to use and not part of the main product line.” There is a 64 bit version 4D Internet Commands which tells me it’s being updated and I see nothing to indicate that it is considered legacy.

list box entry issue

2018-09-05 Thread Chuck Miller via 4D_Tech
Hi All, Environment 4D v15.6 client server I have an array based list box where there are 3 arrays. Only array 3 can be entered Under the list box object I have the following code Case of : (Form event=On Load) //EDIT ITEM(DefaultValue_ar;1) : (Form event=On Double Clicked)

RE: v13 - screen redraw

2018-09-05 Thread Chip Scheide via 4D_Tech
Thanks Stephen, I got it! On Wed, 5 Sep 2018 14:43:13 -0500, Stephen J. Orth via 4D_Tech wrote: > Chip, > > Another option is to use CALL PROCESS (-1) and see if that works... > > > Steve > > -Original Message- > From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Chip

RE: v13 - screen redraw

2018-09-05 Thread Stephen J. Orth via 4D_Tech
Chip, Another option is to use CALL PROCESS (-1) and see if that works... Steve -Original Message- From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Chip Scheide via 4D_Tech Sent: Wednesday, September 05, 2018 2:37 PM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc:

Re: table/field token

2018-09-05 Thread Keisuke Miyako via 4D_Tech
it could be that the token syntax for tables and fields has been missed by engineering when the interpreter was rewritten for object notation. in fairness, though, I don't think it was ever documented that the table or field name could be omitted in token syntax. I know it worked, and sometimes

RE: table/field token

2018-09-05 Thread Timothy Penner via 4D_Tech
Hi Richard, > > * Starting with 4D v16 R4, "." and "[]" characters are no longer allowed in > > names of tokenized objects. > I take that to mean they are no loner allowed in “new” names of tokenized > objects. I take it to mean they are no longer allowed in tokenized objects, **existing or

Re: [v16.3 64 IC on El Capitan] Receive file

2018-09-05 Thread Jörg Knebel via 4D_Tech
> On 5 Sep 2018, at 10:40 AEST, Keisuke Miyako via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > of course. that is not a good enough excuse, > but I wanted to mention it as a weak explanation. Thanks Keisuke. That means I’ll use your cURL only.

Re: [v16.3 64 IC on El Capitan] Receive file

2018-09-05 Thread Keisuke Miyako via 4D_Tech
I don't mean that it is obsolete or deprecated. I mean that the basic design and feature set is pretty much the same as v6.8 (1999) because the focus has been placed on keeping it alive, not to give it a new life. true, there have been efforts over the years to support Unicode, UDP, TLS email