I have a rather complex form where data entry takes place at the child and grandchild levels and it uses several conditional objects to show or hide sections of the form's tables until some pertinent data is filled in. The problem I am having with this form is that currently it runs filtered by a query that seems to be what may be messing with the updating of the child table indexes. So I am trying to get rid of the need for this query as the means to show the linked records for a particular date.
One of the things I am trying out is to have a one record table (SCHEDHDR) with one field (SCHEDATE) as the header for the set. I want to initially open the form to today's date which most often will not have any linked records yet. But I also want the option to let the user pick a previous or future date from the calendar smart field and have the set links refresh. Which doesn't work directly just by changing the header date, so I recall the form in the schedate field's OnChange event and that seems to work - so far.
In the original design, I used a shared variable on the form to change the date and refresh the query. But if the user moved to a date without links the conditional objects would still display briefly or when adding multiple new child records, the query would get out of synch and the only fix was to close and reopen the form.
The other idea I tried was to prepopulate the SCHEDHDR table with business days. But that is also fraught with problems if new header dates are needed.
Changing the set header link field and recalling the form in that one place seems the easiest way to simplify this form. Is anyone else doing this OR has abandoned this idea? It would be good to know the reasons before I tackle changing a bunch of scripts...
apptsch_set.png
One of the things I am trying out is to have a one record table (SCHEDHDR) with one field (SCHEDATE) as the header for the set. I want to initially open the form to today's date which most often will not have any linked records yet. But I also want the option to let the user pick a previous or future date from the calendar smart field and have the set links refresh. Which doesn't work directly just by changing the header date, so I recall the form in the schedate field's OnChange event and that seems to work - so far.
In the original design, I used a shared variable on the form to change the date and refresh the query. But if the user moved to a date without links the conditional objects would still display briefly or when adding multiple new child records, the query would get out of synch and the only fix was to close and reopen the form.
The other idea I tried was to prepopulate the SCHEDHDR table with business days. But that is also fraught with problems if new header dates are needed.
Changing the set header link field and recalling the form in that one place seems the easiest way to simplify this form. Is anyone else doing this OR has abandoned this idea? It would be good to know the reasons before I tackle changing a bunch of scripts...
apptsch_set.png
Comment