ScriptCase v8.0.002 (08-07-2014 23:51)

Scriptcase 8 Changelog
#1

New functionalities

  • Added option to use SSL on SMTP in the creation of the security module.

Specific correction

  • Fixed syntax error when clicking on the detail of the Grid.
  • Fixed accented words of the Report PDF in converted applications.

Bug

  • Fixed SQL error using virtual fields in the search of the Grid.
  • Fixed display of images in the preview of the menu after conversion.
  • Fixed option to use layout (re-sizing) in the treemenu.
  • Fixed issue after changing values ​​in the format of the form.
  • Fixed error when restoring backup containing tasks on TO DO.
  • Fixed behavior on the menu application using macro sc_menu_disable on mobile devices.
  • Fixed security behavior in the menu items on mobile devices.
  • Fixed behavior of dynamic menu (using macros) on mobile devices.
#2

After this update the New Button in editable grid view form applications, still does not work.
The result is that I can update or delete items, but I can not add new details in the detail grid view of a master/detail application.

I think this is a big problem, when you think it can be solved?

#3

forms and control applications are not opening on mobile if security is enabled. message “unauthorised user”. grid is working fine. calendar not checked. all my mobile projects have been stuckup. please look into the matter. if possible reply me on my email saumil@skillbiz.in

#4

[QUOTE=ajhernan;25645]After this update the New Button in editable grid view form applications, still does not work.
The result is that I can update or delete items, but I can not add new details in the detail grid view of a master/detail application.

I think this is a big problem, when you think it can be solved?[/QUOTE]
Hello,

I’m using the latest version and could not simulate your problem.
I created a form with editable grid (view), and found no problems.
Tell us a bit more about this problem.

#5

Hello,

We are fixing this problem to be released in the next update.

#6

[QUOTE=John L. Santos;25650]Hello,

I’m using the latest version and could not simulate your problem.
I created a form with editable grid (view), and found no problems.
Tell us a bit more about this problem.[/QUOTE]

Hello John:

The problem appears in production environment, but not always (in development environment works fine). If you use a table with a first-level foreing key, New Button works fine, but if you have a second-level or higher-level FK the New Button does not work.

If you look at the diagram of the accompanying drawing a editable grid view on Table 3 fails when you click on New Button.

diagram.jpg

#7

[QUOTE=John L. Santos;25652]Hello,

We are fixing this problem to be released in the next update.[/QUOTE]

please…if possible do it on urgent basis…as 3 of my projects are held up because of this…we are using webview in android app and forms and controls are not loading… i have not checked the calendar application.
also please add back/exit button in calendar.

#8

when is the next update??

#9

Internal Server Error while updating SC. How get rid of this?

#10

[QUOTE=ajhernan;25655]Hello John:

The problem appears in production environment, but not always (in development environment works fine). If you use a table with a first-level foreing key, New Button works fine, but if you have a second-level or higher-level FK the New Button does not work.

If you look at the diagram of the accompanying drawing a editable grid view on Table 3 fails when you click on New Button.[/QUOTE]

Hello again John!

Forget my post the problem was the configuration of the character set. I have indicated utf-8 in the connection settings and everything is back to work perfectly …

Thanks for your time

#11

[QUOTE=John L. Santos;25650]Hello,

I’m using the latest version and could not simulate your problem.
I created a form with editable grid (view), and found no problems.
Tell us a bit more about this problem.[/QUOTE]

Hello again John!

Forget my post, the problem was the character-set configuration. I have indicated the correct character-set in production environment configuration (client_encoding= utf-8) and everything is back to work perfectly…

Thanks for your time