Saving application data...keeps saving!

I had same problem, I changed my browser and it works fine. I think the browser can has conflicts.

Thanks Alvagar, I changed from firefox to chrome…seems to work fine.

I work with latest Firefox versions without troubles. Yes, sometimes, it stucks saving data. In this application, just select other option of the left menu, and message disappears.You can now generate without any problem.

I don’t work with autosave.

Ok nothing to do with changing to Chrome. I did it the change to Chrome, but it is still there. Perhaps V9 solves this or/and I have to buy a new computer. Or clean it up with format…

Unfortunately, this is what’s happening . . . many new features are essentially new bugs (due to dependencies on older buggy-code deemed working). Until the existing set of major
bugs are truly resolved, software stability will decrease, and technical debt will increase, . . . end of product life - no one wants that, and it doesn’t have to be so.

Take the steps to fix the application framework - from the ground-up if necessary - to create something stable and productive.

Chrome has a peculiar way of caching pages and page data - it does this for efficiency, but can lead to head-aches when developing.

So I bought a new laptop with I7, 1Tb HDU, 8Gb Ram, windows 10 and only wamp and sc-v9…complete clean…
What do you think…after a day working the same again.

I can confirm that although it’s a combination of steps that leads to it, haven’t got my finger behind it yet. It simply sometimes happens which you can solve by clicking some other function, but sometimes you can’t get rid of it and need to restart SC. Annoying.

Yes Albert, there are 3 “bypasses”. Start an other application, restart sc, and I have feeling when you empty the tmp folder it goes better.
But I have fear deleting files…
In working it slows down my progress, time consuming.

Regards, Bert

I am not sure, but till now it helped a lot.
I saw that in the V9 folder, there where folders which donot have the full read/write. So because it is me only working on the SC, I decided to give the folders in Netmake all the rights. Even as normal user.
After that I noticed a great approvement. Let wait and watch a little…

All I said before is not the reason. Sorry.

I heard in the seminar from Marcia last Friday that changing the php.ini is the drection to thnk about.
So I changed:
max_input_vars = 6000
max_input_time = 1024

Regards, Bert

At least firefox as I have this issue sometimes.

Instead of using chrome you could also try with firefox developer edition… Maybe that one works better…
Alternatively you can wait or like 15 seconds and then open another exisiting application and voila it works normally again. Be sure to wait at least 10 to 15 seconds…

Thanks rr,

I am not going to wait 15 seconds before opening an other a application. Although I am a little older, I want to make production as you. I am not using SC for playng around and close when something is not working. Ok I could drink a cup of coffee between, but to much is keeping me awake during the night. More and more I come to the conclusion that V9 is not workable on this point. I like the interface and I am not confrontated with stopping bugs, but all is much too slow. In this SC is not a RAD but a SAD.
More worse, sometimes after opening 5 or 6 applications the whole system hangs. Another thing: Sometimes (so ones a 2 weeks) I have to rebuild a complete grid or form because it is corrupt. Further: Most off the times I have to generate an application after a change more than ones before I see effect.
All has to do with saving / memory or something like that.
I mean off course in the development part. I even bought a new laptop with high capacity only for SC. No effect. I mailed Marcia after the last seminar, because somebody mentioned the same.
No answer… The longer I go with V9 the longer the way back…to V8.1. Can somebody tell me what to do? Stopping with SC is not an option. But what? Lett’s at least share some experiences on this point.

Regards, Bert

Hi everyone,
I am not here to pass judgement on SC9. I have earlier on this forum posted a little bit of my early issues when I tested it a bit early on. I really like the new SC9 features and the promise it holds for moving forward… in the future. I am still happily working in SC8.1 and will keep that up on my existing projects. I just can’t take the time out right now to even try converting a 300+ app project - it might just do it 100% the first time - I don’t know. Or I might find there are bugs or issues that get introduced. To me, right in the middle of a big ongoing projects that has active users, I can’t afford to introduce ‘outside’ problems. I have enough of my own self-generated complexity, and anything that rocks the boat is bad for me as a developer.

If I was starting out a brand new project, where I had some time to approach SC9 in a new light, I might at this point try an SC9 development. It seems like Netmake has made some real progress on fixing initial bugs. I hope to really put it to such a test soon, as soon as I get my latest release out on my project. My project could ultimately benefit from SC9 features, like the cool dashboard and better charts, etc. So like you, I have a vested interest in seeing SC9 and Netmake succeed.

Maybe that is something that is worth discussing - a sane approach to upgrading large-scale projects. Here is something I have been thinking about for sometime and I plan on discussing with Netmake soon - adding a unit test system inside SC. Here is my basic idea:

  1. Add a new setting screen to each type of app - Unit Testing
  2. The SC internal database (SQLite still I believe) would store one or more Unit Test, which would store values for any field, global variable and parameter that is used by an app.
  3. Each Unit Test would also be able to trigger any internal event (e.g. our custom code), as well as passing parameters to another app.
  4. Each Unit Test would include an option to simulate a user decision/action - like clicking on a button or whatever.
  5. Each Unit Test would have an expected result - could be either an expected value in one or more field, global variable and parameter - or the calling of another SC app (with expected parameters, etc).
  6. Unit Tests could be run individually by us when we are testing/developing
  7. All Unit Tests could be run as a batch - just like when we generate our apps. Perhaps when we generate app, it could do this by default. We should see a green check when a Unit Test passes, and a Yellow Flag when expectations are not achieved.
  8. Then when doing SC version upgrades, we could run all Unit Tests and be highly confident that the system is AOK.

I believe this would bring a key development principle to SC that is lacking. It would help someone like me who depends on SC as a daily business tool. It would also help Netmake, as they can run Unit Tests on all types of apps in their sample projects, and have a very high confidence that any SC changes they made ‘under-the-hood’ have not broken anything for existing projects/users.

Anyway, I am an SC user who feels all the pain of those who have posted issues here on the forum. The above reflects my personal approach to using SC effectively, along with one of my longer-term hopes. I am not defending Netmake’s approach to how they develop their product, since I am not a part of the organization. It is a very good, rapid development tool - which I still recommend to people and personally use on a daily basis.

I also want to say thanks to Marcia. I know her name comes up a lot here, as she is the face of SC and Netmake to a lot of us. She is a brilliant marketing/Public Relations/ and even online training person. She has become very skilled in using SC, and I think we often forget that she wears many hats. I think everyone at Netmake probably does wear many hats - perhaps too many. As Albert has said, they are not a large company. That has it’s pros and cons:

Pros:

  • Because they are small, we actually know who Marcia is, thru direct contact and/or thru the webinars, etc. Some of us have had contact with other individuals. They are all nice people :slight_smile:
  • Because they are small, they are perhaps more attuned to this particular market niche than a big company would be. There has to be a factor why they produce SC, the best PHP Rapid Application Development system out there.
  • A larger company might not be as responsive at all. When was the last time you knew the name or even had a chance of communicating with head of marketing or a developer at Apple or Microsoft. Netmake is like a mini-Apple, and much more personable :slight_smile:
  • They are obviously very close to their user base in Brazil, which is an advanced economy with many types of projects being developed using SC. That continues to help Netmake keep enhancing SC as a product for all of us.
  • They are smaller and want to keep making the ScriptCase product - a larger company might have ditched us already for a NodeJS solution.

Cons:

  • There is only one Marcia, hence she must be super overloaded and sometimes can’t get back to us. I hope she gets a good vacation and is not too overloaded :slight_smile:
  • They have a limited number of developers who are probably stretched thin, especially when doing a major SC change like 8.1 -> 9
  • They seem to not have enough people to take acre of things (like maintaining a public list of bugs OR upgrading this maddening and outdated version of the forum!)
  • They have a global market but are very centered on their base country (understandable), but that makes them vulnerable to local economy and situations that we may not all understand. Myself coming from USA we are having our own political and economic storms here so I fully understand Netmake. A larger company would have teams in multiple countries and would minimize local/regional effects on business resources.
  • Some of us outside the region may not feel quite as connected to the way they do business where Netmake is located. I think cultural differences are sometimes a big factor with issues many user have - such as lack of timely communication responses, less than optimal transparency, and release of less-than-optimally tested SC versions (e.g. no transparent beta testing), documentation that is not 100% perfect English, etc. Again, these MAY be acceptable business approaches in the region, while not expected by users in USA and Europe for instance.

So my approach is going to keep accepting Netmake and their staff for who they are. They have a successful model that obviously works for them as a company that is still around and thriving. So many other development systems and companies have collapsed over the years.

Let’s try to keep helping each other here in the forum. Thank you each and everyone one of you who have posted suggestions and ideas and help. This is a good community - even if the forum software keeps acting like %#^%5 LOL.

And let’s try to meet Netmake’s staff where they are at now, and keep suggesting and exploring new ways forward together. I need SC to keep working well, as I know you do. That includes a fully 100% functional and powerful SC9.

Sorry for the long winded post, but I felt like we need all need to look at the positives and proceed in that way :slight_smile:
Peace,
Jamie

Yes onmountain…I understand what you saying. I am positive too. That why I said: “Stopping with SC is not an option”.
But I am looking for a solution for the “keeps saving” and the slow working. More memory, more cores, more RAM? The change to firefox did not help.
Could be that I am the only one…or a setting is wrong…I donot know

Regards, Bert

You are not the only one, but happens to you too much times, and probably is something related to your machine.
Last time happened this to me was a lot of time ago.

Could be, but afaik it’s a combination of actions that leads to this effect and it’s fairly reproducable. BUt it’s been a while I looked into it, will try to replicate it again.

Hi Albert,

Would be great if you can reproduce it. If you need some info, please let me know. Or have a look on my screen with teamviewer.

Regards Bert

Problem solved with version 9.0.14…works great now