Thank you, Lahav. Worked.
Still don’t understand why REDRAW( ) doesn’t get a (*; OBJECT NAME) syntax
though …
(But your solution is simple enough)
— Chris
> On Mar 10, 2020, at 7:27 PM, lists via 4D_Tech <4d_tech@lists.4d.com> wrote:
>
> All you need to do is to assign the entity selection
What build version are you using? This was supposed to be fixed after version
18.246179.
See https://forums.4d.com/Post/EN/33231346/1/33265607 (if you are in the
partner program).
John DeSoi, Ph.D.
> On Mar 10, 2020, at 3:18 PM, Sannyasin Siddhanathaswami via 4D_Tech
>
All you need to do is to assign the entity selection object to itself to
trigger an update, as in
Form.my_Entity_List:= Form.my_Entity_List
Lahav
-Original Message-
From: 4D_Tech <4d_tech-boun...@lists.4d.com> On Behalf Of Chris Belanger via
4D_Tech
Sent: Tuesday, March 10, 2020 7:03
Sorry for not including that detail. It is an entity-selection listBox. I had
initially written more detail about my issue and decided perhaps it was too
verbose (a bad tendency of mine).
It has the same ‘REDRAW( )’ issue as the subform that contains it — no way to
indicate the object. Since
Me too !
> Le 10 mars 2020 à 21:18, Sannyasin Siddhanathaswami via 4D_Tech
> <4d_tech@lists.4d.com> a écrit :
>
> Yes. Dot notation works fine.
>
> Sannyasin Siddhanathaswami
> On Mar 10, 2020, 12:11 AM -1000, Vincent de Lachaux via 4D_Tech
> <4d_tech@lists.4d.com>, wrote:
> Is the database
> On Mar 10, 2020, at 9:17 PM, Sannyasin Siddhanathaswami via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> for instance, could it be that the table does not have a primary key?
Changing something in structure and not having primary key might cause the
issue.
Milan
You were not hallucinating. When a field name is changed in the structure, the
app must be restarted for the change to be recognized.
Keith - CDI
> On Mar 10, 2020, at 3:17 PM, Sannyasin Siddhanathaswami via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> Ok. I guess I was hallucinating or
Yes. Dot notation works fine.
Sannyasin Siddhanathaswami
On Mar 10, 2020, 12:11 AM -1000, Vincent de Lachaux via 4D_Tech
<4d_tech@lists.4d.com>, wrote:
Is the database accept dot notation ?
vdl
**
4D Internet Users Group (4D
Ok. I guess I was hallucinating or something. It works today with one
exception. If I change the name of a field (to remove spaces in field
names…..), the new field name doesn’t work in an orda query. I get this error:
The "Account_Name" attribute cannot be found in The "Deposits" datastore
Hi Chris,
What's going on in the subform that's not updating?
On Tue, Mar 10, 2020 at 12:05 PM Chris Belanger via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> 4D continues to NOT QUITE truly and fully support its object notation, and
> the inability to get a pointer to an object attribute continues
4D continues to NOT QUITE truly and fully support its object notation, and the
inability to get a pointer to an object attribute continues to confound.
The latest issue involves an attempt to use REDRAW( ) to redraw a subform that
is named, but whose ‘variable or expression’ as an OBJECT (not a
Never seen this. Remember everything in ORDA is case sensitive.
> On Mar 9, 2020, at 10:08 PM, Sannyasin Siddhanathaswami via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> When I do a ds.Table.query() using a field/attribute of a non-indexed field,
> I get an error.
Is the database accept dot notation ?
vdl
**
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
I have the same issue.
V18
Mojave
Cordialement,
Bernard Escaich
> Le 9 mars 2020 à 21:24, Sannyasin Siddhanathaswami via 4D_Tech
> <4d_tech@lists.4d.com> a écrit :
>
> Aloha,
>
> I’m having trouble getting the new comment blocks to work in v18. Seems silly
> simple but doesn’t work:
>
Hi,
Effectively, there was a trace of a method from the AJ_Tools_UnitTest component
in the AJ_Math component that makes an unwanted dependency.
This is fixed and you can now download the 1.2.2 version which doesn’t have any
dependencies.
If you want to look at the unit tests, you must launch
the OP is already solved, but on a related topic:
as documented, XML SET OPTIONS only applies to newly created elements.
https://doc.4d.com/4Dv17/4D/17.4/XML-SET-OPTIONS.301-4882274.en.html
so you might ask, what about existing XML documents?
---
until v12, there was a trick to use the
16 matches
Mail list logo