showFormInDialog losing found set

Classic Servoy
1

I have a form that is a list view of records. There is a method that shows a form in dialog to show more detailed information than the list view shows. The problem is when you click inside of a field, and then click back out, it loses the found set. So, it goes something like this.
Your looking at a list view, click a button, you then see more detail with a form in dialog. You click in a field, then click out on the form background, and the found set changes from 1 to 0.

The button on the script to show the form in dialog does this…

forms.prms_entryDetails.controller.loadRecords(prms_entry_to_prms_entry);
application.showFormInDialog(forms.prms_entryDetails,100,80,550,720,‘Patient Details’,false,false,true);

2

This shouldn’t be happening and I couldn’t reproduce the behavior with a simple test. So a couple of questions:

1/ do you have a method firing on the dialog form (onShow, onLoad)?

2/ any methods getting fired when you change data or exit a field?

3/ is the relation “prms_entry_to_prms_entry” a match on the id field or something else?

3

Thanks for your response.

david:
1/ do you have a method firing on the dialog form (onShow, onLoad)?

No, no methods fire

david:
2/ any methods getting fired when you change data or exit a field?

No, none

david:
3/ is the relation “prms_entry_to_prms_entry” a match on the id field or something else?

It is a match on entry_id which is the PK for the prms_entry table.

4

That is interesting. I have seen quite a few occurences of a problem where those self-relations went wrong. In my case there is a problem using self-relations when creating new records. In some cases Servoy tries to update the primary key of the newly created record with the primary key of the previous record, coming from the 1:1 relatonship (so all of a sudden the self-relationshhip looks like 12345:12344 instead of 12345:12345) I haven’t been able to really make a reproducable case, but it does go wrong once in a while. Since the database refuses this update due to a constraint violation (update of the PK using an existing PK), a rollback occurs.

If you can reproduce your problem, please provide a sample solution to Servoy, because they might be able to also fix my problem. Do you get some error in the log? Could you start with a stacktrace and have a look at the statements getting fired?

5

if anybody can make a reproduceable case for this in a sample solution please make a case:
http://crm.servoy.com/servoy-webclient/ … oy_support