NelsonFS

This component is for compatibility with old projects.

I need this too!!! A Cancel Button is very usefull to stop processing!

"-r" .. it's a old option in delphi start command line. Easy way... open regedit, export key "HKEY_CURRENT_USER\Software\Embarcadero\BDS" to file. Open file, replace "\BDS" to "\BDS_Test". Save and import reg file. To start delphi using new profile: "C:\Program Files (x86)\Embarcadero\Studio\20.0\bin\bds.exe" -pDelphi -np -r BDS_Test

Inside RestDataware, you can create a method and publish it, creating a connection object variable (like firedac / zeos), process it and finally destroy it. Or, you can use the one automatically configured by RESTDWDataBase. TServerMethodDataModule is always created automatically and destroyed. As for using Firedac with cache, be careful when synchronizing when the connection returns. Because another user can change the data that was cached on another computer, there you have to work with concurrency errors, in addition to the risk of losing launches due to the permanent loss of connection. In this case, the user complains that he made many postings and lost the records. This cache option is great if the user continues to include / change / exclude and maintain search data, but when he returns online, you have to deal with problems that may appear. Attention, the server should not keep too much in cache, otherwise you will have a lot of problems with high memory consumption and risk of deadlock in the tables. In my opinion, the best thing is to keep the memory on the server side to a minimum. Because when the server goes down, or returns, everything continues. If you had caches, there are problems with restoring the point you were on. And that is what the REST way of working has the advantage.

Transform you system to work with rest server.. uses DataSnap or RestDataware. Each procedures/functions will create a connection in runtime, execute, and return a json. In UniGUI project, create process to call this rest server e process this json. In future, you architecture will works with any type of client side and will consume lowerest resource.

Before create pdf, in your component, set permission... Check if you component permit modify.

olá.. já existe alguns grupos no whats.. o melhor seria no telegram pois cabe muito mais.

Updated link https://mega.nz/#!f9U31ShZ!TVMUEYGOlV-7Dp7TxyNt68BtXfRW2Pt7SLTS-0JQAS0

other solution.. in ExtEvents: function afterrender(sender, eOpts) { sender.btnInnerEl.setStyle('white-space', 'normal'); }

try just add in ServerModule.CustomCSS: .x-btn-button { white-space: normal; word-wrap: break-word; }

Cria no Telegram.. lá cabe muito mais...

Remote deployment is very useful, but would be more practical if some features exists: - In an environment with many connected users and multiple nodes, when it is detected that a new version is available, show a message that the user would have X minutes or force to close the application. Hyper Server would send a message to the TUniServerModule of each application that could display that message to the user. - Capture remotely the information of several servers running Hyper Server, and thus with an administration centralized know to be there are many crashes and excesses of memory consumption, close sessions remotely. - In case of errors in new executables, to be able to return an old version of the application without having to recompile, it would be a rollback. - Remotely be able to restart or quit Hyper Server. It could easily be done when it detects a particular file in the deploy folder. Example, when the file 'reboot.dep' exists, all applications of the nodes would be closed. Or when the 'quit.dep' file exists, terminate the 'hyper_server.exe' application, and so it would be possible to remotely update the hyper server executable. Farshad Mohajeri, is it possible to create these options?

Hi Tested on version 1.50.0.1479: Everything worked beauty. Cute button.

Please, tell to us the results.