How to reset the entire project applications by MISSING ONE MOUSE CLICK

Scriptcase 8 Bugs
#1

Reported this issue numerous times and today it did happened to me again. Here is how to damage the entire project.
Have ate least 100 or more Apps (I have a project with about 360 Apps).

  1. Go to Dictionary and open existing one
  2. Select all tables and do “Synchronize Dictionary”
  3. Once this is done go to “Synchronize Applications”
  4. If you forget uncheck “Data Type” on the PROPERTIES panel - all data types in the fields you have modified for last few weeks or months will be gone !

Due to the fact that some NetMake developer did not care to preserve data type settings which has been modified in the Apps you can loose lots of work. I accidently left this field checked I have lost (roughly) about 20 hours of work.
Yes I can go and modify the settings for each field in every App but this will take me about 20 hours if I want to do it manually. How god is SC if I keep loosing time undoing things like that ?
I reported this numerous times and of course it was ignored. It did not bothered me so much when working on a small projects with 10-20 Apps. I could go an make changes manually but with 400 Apps it will drive one crazy to fix this crap!

Does anybody know any way of restoring field types (other than restoring from backup) ?

[ATTACH=CONFIG]n73549[/ATTACH]

The main problem here is that the only changes that should be applied are those which are referenced in database. Another words - there is no Minimum size, Mask, etc value in SQL database. Also when the text field is changed from “plain text” to selection bog (it is still text) those settings MUST BE PRESERVED when updating Apps from dictionary. At this moment the dictionary can do complete destruction of the entire project - as it happened in my case. Yes I can restore from backup but it still will take me few hours to get to the point where I was.

One other thing I need to mention to anybody from NetMake reading this. IT IS A BUG! Bug in a software if not the only case when the Error message pops up on the screen - please consider this and finally fix as it is big issue!

THIS PROBLEM REALLY NEEDS TO BE ADDRESSED and as many other so far was completely ignored.

dictionary_bug_06.jpg

1 Like
#2

It will change the fields back to it’s original state like lookups become edit fields again. I agree that it might take a lot of time to correct. However when you change the fieldtype back to lookup the old settings where preserved and restored. But very inconvenient yes. My option was to uncheck all items by default except the label which is needed for translation. I always advise to uncheck all and then set the options you need. It’s not a bug, but need to change, I agree.

#3

It is Very dangerousous. Thanks Albert for this information is very important for us.

#4

Yes Albert I know about it, but imagine going through about 150 FORMS (where some have 12-24 of those fields ) and fixing every ListBox, Check box, radio Box etc…
THIS IS A NIGHTMARE ! It happened to me already twice but I have never had this many apps in one project before so this happens it is basiacally a disaster !
since SC stores the old settings somewhere, perhaps they could add some button or link to restore those settings with one click but of course they ignore everything and NET MAKE ignorance on issues like this one makes me super mad >:(

…and of course when I post a complain to bugs department they will reply “it is not a bug, but possibly missing feature”
I don’t really know WTF is going on with this company

#5

Hello,

This case has been reported to our development team.

Thank you.

#6

John - you keep saying this same BS over and over, nothing has changed, none of this got fixed. In my eyes you guys loosing all credibility - YOU (almost) NEVER KEEP YOUR PROMISES.

It is not personal but I do not what is going with your company. Something is very very wrong. Once again I REPORTED THIS ABOUT TWO YEARS AGO ! One of NetMake members (not sure if it was you) stated the same thing you just did. TWO YEARS LATER THE SAME PROBLEM EXISTS. [B]How can you guys expect us (users) to recommend your product to others ???

TODAY I HAVE TO SEAT DOWN AND START RE-DOING ALL FORMS IN THE PROJECT - THIS WILL TAKE ME PROBABLY AT LEAST 2 DAY, YES - I SAID TWO (or more) DAYS just because you ignored my and other requests. I would llove to put any of you in a position when you go to work (i.e. tomorrow and work FOR FREE for 2-3 DAYS). HOW YOU YOU LIKE IT ?

Art[/B]

1 Like
#7

After a brief discussion we realized that only the “Label” should come checked and therefore you won’t have major problems because you just concluded the data dictionary steps in a hurry.
Thank you.

This will be released in the next version.

#8

NO - you missing the point! I used other tools in the past which used to work similar to SC with the same concept of a dictionary. There was a simple option for each field called FREEZE. When you checked it all dictionary property changes for that field were simply skipped when updating dictionary was taking place. I posted about this 2 years ago BUT OF COURSE YOU IGNORED IT. This seems to be rather simple to implement (perhaps I’m not aware if not) but the fact is that if you would pay attention to suggestions you would have this implement it by now.
I reported this problem long time ago. While I understand this is not a bug it needs serious attention. It irritates me terribly when everything that is not considered a bug is ignored and you (NetMake) guys spend more time on arguments weather it is or not a bug instead spending your time and energy on making customers happy with your product.
You keep posting the same BS statements about issue being reported to keep people calm and hoping that it will be fixed, but then if somebody spends enough time and energy to track the problem he comes to the point where it simply shows that you do not care because to issues reported years ago (and confirmed with those statements (being reported for fix) are still unresolved.
If you would spend today all day I could make a list of at least 30-50 issues - Reported, Confirmed (by you) and NOT FIXED. I do not have that time neither want to be your tracking guy OR bugs tester. The fact that you can release a screen with NO LABELS just shows that your quality control does not exists! PERIOD

You might thing - why am I so negative about SC ? I am because stuff cumulates over years and I was stupid enough to keep development instead switching to another tool, perhaps more tedious but less stressful. If at least I would see some changes in company attitude I would have hope that some things might get better. At this point I’m very very upset because there is no week I could work with SC and have no issues (which I cannot control).

I would like you to seat down by my desk and go through 150 forms and update the fields one by one and spend 2-3 days doping it and then few weeks or months later if it happens again do it again and again. Perhaps you would then understood why people get mad at NetMake.

#9

No your statement about checking LABEL field only is not true because when I change the field size or type from SCTRING to NUMERAL it needs to be updated. When DICTIONARY IS updated and then the Apps are updated there should be a warning message (or selection message) to ask user weather to update field properties (i.e change CHECKBOX field back to TEXT). That is another confusing problem. The text field in SQL database and TEXT field in SC are not the same things - why did you call it TEXT while it is STRING. Keeping STRING and TEXT as separate entities eliminates confusion. For SC one line TEXT and 100 line TEXT is the same. For SQL it is not.
One again simple FREEZE parameter next to the field will protect that field from DICTIONARY changes. To make it more flexible you could also make FREZE parameter with few options (i.e. Freeze Field Size, Freeze Field Type, Freeze Field Label). The fact that the field LABEL gets updated and destroyed on the FORM makes it even worse because now one must update all the labes which are not exactly as in database. The whole DICTIONARY updates are just CALL FOR DISASTER !

#10

I think it is very important to take into account all these recommendations made by the people of the forum. Especially by Arthur who is documenting every error he is seeing inside SC. So we do not waste so much time investigating how to solve these problems.

#11

I think I read enough and I’m not interested in what you think, neither in your misleading conclusions.

If you want to discuss something, create a topic in general discussion and maybe I will argue with you there.
Lets keep this to bugs and not strange discussions.

If you want to suggest something now, you can suggest and we’ll analyse it and discuss together.

Our culture is changing, we want to be more active in the forums and tightener the relationship with our clients, so live in the now and stop living in the past.
You keep saying “years ago” like it matters. It doesn’t, so stop acting like a scratched vinyl saying the same thing over and over again.

#12

@alvagar I agree with you, I want to help all our clients. NetMake has a long time relationship with Arthur, however in the last year its becoming very hard to sustain this.

If, by any chances you think he’s just a little rude here, when he contact us directly its often very frustrating for the guy who handles the bugs e-mail.
And I try to defend him, he’s a client and etc… I think his criticism is useful, kinda like a necessary evil…
However its hard to support him when he treats my team the way he does.

I’m a pretty honest guy, so that’s my thoughts and not my the company opinion.

#13

Our culture is changing, we want to be more active in the forums and tightener the relationship with our clients

As a newbie, that sounds good to me.

I don’t want to get into the middle of this. But let me say, I know some can use really heated language that can be off-putting. But I must say that whenever I read a certain senior member’s posts, temperature aside, the complaints voiced seem real to me. As a newbie ScriptCase’s commitment to fixing bugs and improving functionality is really really important. I use another product that is much more powerful than SC, in my opinion. But nonetheless, I’ve been drawn to SC for other reasons (and purchased it). Fixing bugs and improving existing functionality will determine whether, I for one, stay or go. I’m glad to hear what sounds like a commitment from ScriptCase to improve things.

#14

Everybody is talking from his own perspective and things on the other side look sometimes different. I understand the point of view that NetMake is overwhelmed with tasks. I also understand the point that in order to make and grow SC NetMake developers need to make money somehow. I understand the fact that they want to make more sales and (somehow) can even accept the fact that they push commercial adds into the IDE.

What I do not understand is that the attitude towards customer, bug fixing, improving documentation, language and attention to details HAS NOT CHANGED for the last 3 years much. By saying much to be fair I have to say there are some changes but they are minor and no in the areas which are crucial. I also do not understand the fact that little things which can be improved in minutes ARE NOT IMPROVED OR FIXED.

Cavandinha - you are perhaps to young to understand or perhaps did not have enough experience using other products, tools, dealing with other companies (as a client). The market today is very demanding. You might have the best product on the world but with the poor support you will soon drawn in a crowd of other crappy products. I usually live in a present moment but sometimes the PAST IS IMPORTANT because it gives us a comparison if things are improving or not. That is why I often refer to BUGS UNFIXED FOR YEARS. That is why I’m being rough.
YOU HAVE TO REMEMBER - WE ARE THE ONE’S WHO GIVE YOU THE MONEY not the other way around. I understand all people in NetMake DO THE BEST THEY CAN, but sometimes doing the best means OPEN FOR CHANGES. You company (and I understand it is not your personal fault or decission) is not open for changes and things continue they way they used to be. This for most users (including myself) is interpreted as IGNORANCE. Another words “we say ABC” and NetMake does “XYZ”.

At present stage I would be willing to pay you upgrade price and get SCRIPTCASE v9 with no new features implemented. Just have all the bugs fixed. YES - I WILL BE HAPPY TO PAY FOR YOU TIME TO DO THIS. I bet most users here will share this same feeling. Then I would be happy if you ASK MEwhat features would I want to see in SC v10, even perhaps make a survey among us what is more or less important. YOU DO NOT DO SUCH THINGS, YOU MAKE YOUR OWN DECISIONS and that’s another sign of ignorance. Then when users start to complain you sent them warning Emails and that is SIGN OF ARROGANCE.

I do not know who is making decissions in your company but pass this message you CEO. There is a tipping point and one day some unhappy users will start sharing their feelings on other social sites (FB, YT etc…) and that is something none of us here wants. If not enough changes are made soon in COMPANY vs USERS relations this might be very likely scenario.

Once again. I reported the issue mentioned in a first post over 3 years ago. If anybody from NetMake states that this fact is unimportant then further discussion here makes no sense!

#15

Your conclusion nailed it all.
Why the big wall of text? I don’t know. But its good to let things out.
Know that the staff from 3 years is very different from the current staff, so if you put this on perspective… the past makes no sense.