Missing primary key despite correct db structure

Scriptcase 9 Bugs
#1

One of my table had a primary key of small int. scriptcase will not accept this as primary key.
I changed the table to a primary key of type int, updated the data dictionary, checked configuration within the application. The application has erverything properly set and scriptcase still reports: Application cannot be generated: Primary Key field undefined.
Configure the primary key in: Application->Form Settings->SQL Settings.

The conclusion: This can only be corrected by deleting and recreating the application. There are many processes in scriptcase that cannot be undone and produce unexpected und unexplicable behaviour. I have had to restart a complete software project with scriptcase because of this, loosing an enormous amount of time!

I am fully aware, that many complex software systems have this behaviour. Therefore my criticism points to the lack of information. Scriptcase would help the users enormously by publishing this effect. In the end they will have customer satifaction and increased sales!

I scriptcase reports illogical errors, just delete and start afresh!

#2

Here is a list of areas, where later changes may or may not be actualised:

  • project->run project will not show change in template verified in run application
#3

Hello Sir,

Scriptcase does allow you to create a table with a small int as primary key.

Dou you have any more information that would help me to understand your issue?

Your suggestion about Scriptcase’s behaviour information will be delivered to our developer team.

#4

Hallo robertoferraz

At the moment I can only refer to the example in this post. I spent a lot of time trying to understand why scriptcase would behave strangely. Then I restarted the whole project afresh, after which those curious issues disappeared. One of the culprits seems to be the security module. Once this is selected it changes the project in a way that is not transparent. Any change that affects the security module produces unexpected results and corrupts the project beyond repair.

For the moment I have to develop and test the project without any security. Only at the end, after cloning the project, I will add security. Like this I hope to succeed in the end!
Regards Christian

#5

One of the reasons, this message happens, lies in caching. This happens specialy when changing the underlying database table.

How to correct when all locations where the primary key can be set ( ) have been set ?

  • Close the application and open it again.
  • Close the project and open it again.
  • Close the login to scriptcase.
    One of those has so far always helped.
#6

i have same issue, this happens when I alter table in MySql, and after I synchronize table, error occurs. I think I agree with you, I think I need to recreate the application again only because I alter table.really frustrating. I hope SC teams can do something about this