Hello,
I am working on a solution with DBF tables.
Doing a new record() in one of them takes too long (45 seconds). It doesn’t happen in other tables.
Other weird thing is that it happen the first time since i open the solution, the second and the others new record go faster (2 seconds). If i close and open the solution again, the first new record go slow and the others normaly.
Thanks in advantage for your help.
I think that the problem of the delay doing a new record in that table is that it has 2 “row ident”.
I want to eliminate the “row ident” in order to confirm my idea. I did it from developer But it doestn take effect since when the solution is imported the folow advise come up:
"The server version of the column ‘id_exm’ of table ‘linplafac’ in server ‘pruebadbf’ has row_ident constraint while in the import version it has constraint. "
How can i take off the “row ident” in the server??
I wanted to say how problem was solved the.
maybe is helpfull for other poeple.
The delay stopped when i create the new record from the relation instead of the form.
I mean:
analisis_to_cabplafac.newRecord()
instead of:
forms.frm_cabplafac.foundset.newRecord()
mo_ca_mo,
The difference between the 2 is that when creating the record via the relation, the relation parameters are filled in automatically when newRecord is called via the relation.
But that should not make any difference in performance, assuming you fill in all the needed fields when creating the record from the form foundset.
Also note that newRecord() is purely an in-memory action, only when the record is saved, the db is accessed.
Are you sure the records field values are the same in both scenarios? may the db wants to update some indexes/check foreign keys with null fields.
Rob
Thaks for you answer.
Yes the scenario is exactly the same in both cases. And i am testing this issue always with the same fields values.
the difference could be that i am working over DBF tables?
I am not sure, i am new working on servoy, but It seems that when the delay is excesive all the table is “looked” twice, one for each row_ident.