nuBuilder Forum

Hi

I would like to make you aware that today after I updated from nuBuilder Forte 4.5 - DB Version: V.4.5-2021.06.11.00 - Files Version: V.4.5-2021.06.14.00 INTO >> nuBuilder Forte 4.5 - DB Version: V.4.5-2021.08.05.01 - Files Version: V.4.5-2021.08.06.01, ALL listed records from any of the Browse Type Forms are no longer clickable, see below graphics. To solve this problem, I had to convert all Browse Type forms into Browseedit Type forms as it is the only way records are clickable to obtain details ( in my case interface 123). So far, after updating, I have not encountered any other problems , I am still inspecting to see if anything else has changed. Thanks

A Browse (only) form is not supposed to be used to Edit records. The right type is "Browse and Edit".

Hi Kevin

Thanks for your reply.

Before the update, all records listed on the Browse Type forms were clickable, I used them mainly for a certain group of people to view details of them only and not to edit them.

I have found the Browse Type form is much more flexible in presenting data and graphics, than the Browse and Edit form. And In combination with applying level permissions, I was able to do custom views and prevented certain people access to the Browse and Edit forms as I did not want them to change or even view certain data.

skyline101 wrote: Before the update, all records listed on the Browse Type forms were clickable, I used them mainly for a certain group of people to view details of them only and not to edit them.

I'd like to understand how the Browse was different from a Browse/Edit.
With the browse you could also edit/save the form if objects were present.

With the browse you could also edit/save the form if objects were present.

That is precisely what used to happen.

YES, with Browse forms, one can still edit/save if the objects are present but in my case, I purposely made many of those objects not present allowing me to present data differently to a particular group of people, therefore limiting data they can view/read, edit or save in addition to their own level of login access.

Having Browse you can still add a "Redirect To" form in the form properties dialog.

Hi Kevin

I would like to report one more error that I never had before the update, see attached graphic.

Like before, to a new Browse/edit form I added a new subform that contains a look up object. After I select any record pulled from the lookup object, the error appears for those I have saved. The system allows me to click on all records from the Browse/edit list, except the one(s) I have saved with the fatal error.

To temporarily get rid of the fatal error showing up on saved records, I went to the subform table on my db and deleted them. I checked the NuDebug Result entries and nothing shows up in there. I decided to delete the subform and all its objects and generated a new one but the problem persist.

Kevin, have you seen that fatal error before, if so, how can I fix it?

That is a great idea, I will place a redirect to the Browse forms, thank you.

skyline,

It seems you have a problem with some of the custom PHP you have written (maybe by creating 2 procedures both called getForms()).

One way to check if you have done this is to create an sql backup of the whole database and do a search for "getForms()" with a text editor.


Steven

Hi Steven

Thanks for your superfast reply. I am not using any custom php.

I decided to take my back ups before the update and reconstruct what I have done and both the Browse Forms and Subforms work without any problem.

Before the update, whenever I tried to set up a new subform within any Browse/edit form, the system will ask me to register it on the db by showing a blue + sign, see graphic #1 below.

After the update, the system was changed as it no longer shows the blue + sign whenever I am adding a subform to a Browse/edit form, see attached graphic. I believe this is the reason why I am getting the fatal error.

Now that I am running the previous version, I am no longer experiencing any errors.

Hi Steven

Before the update, I had one Browse/edit form with 3 subforms. After the update I added one more subform to the same Browse/edit form and that is how I got the fatal error. Now that I went back before the update, I added one subform to the same Browse/edit form and I am also getting the fatal error with 4 subforms.

Is there a limit as to how many subforms can be added to one Browse/edit form?