parent datasource table: FELADAS parent ID field: FELADAS
child datasource (both section 2 and section 3) : FUVAR child ID field: FELADAS
Yes, requery() works well, dataset is OK (while grid...
Type: Posts; User: strato
parent datasource table: FELADAS parent ID field: FELADAS
child datasource (both section 2 and section 3) : FUVAR child ID field: FELADAS
Yes, requery() works well, dataset is OK (while grid...
but there is another issue as well ...
at the first moment, the picture same as at you , but after clicking Next record ...
2342
the grid become empty
2343
page works well, the third section...
Hi Barry,
take a look at the bottom nav bar... '1 of 3'
2341
no more tabview. the parent is a simple form section, the child is a grid section. The problem is with the vt. Everything works fine with automatic relation. However, in the case of Vt, the automatic...
that's all
proc feladas_fuvarlevelek_parentdatachanged()
// insert your code here
private cFeladas, ca
cFeladas = feladas.feladas
ca = cursoradapter("fuvar")
if...
here is the output in performance metric (the blank lines I inserted for myself to understand better)
the datasource of the first section ("azonositok") is "FELADAS". "FUVAR" is the name of...
is it important to have '1' in the name of the section?
In my case, there are 3 sections with letters only names. Going from top to bottom on the page:
"azonositok" (identifiers) - form section...
more precisely, the navigation bar (also) works, but ...
I would like a little help with programming the manual relation setting (parentdatachanged delegate). I wrote this,
proc...
the trouble is I don't understand ...
Don't understand what makes it wrong and i don't know how to fix it
.... I'd rather start it from scratch
no, there are two form sections here (and a grid in tab 2). First I set up an automatic relation, then I changed it to manual (because it didn't work) for which I wrote the parentdatachanged...
my Page has 2 sections (first is a tabview with 2 tabs). The navigation bar does not work. What can I do?
I see that the record number above the slider corresponds to the record count in the table...