Label Field Not Disabled

Scriptcase 7 Discussion
#1

Hello everyone,

I have a primary key field that I set to label, however when I run the application the field allows data to be entered into the field. This is a particularly strange and annoying problem because I have other forms containing primary key fields with identical parameters, but those fields are actually behaving how they are intended to.

I’ve even gone as far as creating an entirely new form, but the bug is persisting. Has anyone ever had this problem before and discovered why or how to resolve it?

#2

2 questions:

1.- is that field set as PK in your database?
2.- is that field set as PK in Scriptcase?

Regards

#3

hi, did you try to mark it as read-only?
another idea PK usually is AI and we hide it back, why don’t you move it to “not shown” section from “edit fields” and create another one scriptcase based as label to copy the value from the main field, something like {field}={label}

#4

Kafecadm: Yes it is a PK in the database, however it wasn’t at first. This had already occurred to me as a potential problem, so I examined the table in the database and noticed that the field was NOT designated as PK (I didn’t make these tables). So I updated the field in the database to be a PK and went into scriptcase and still have the problem. This was around the time I decided to try to just remake the form, because the “synchronize table” button wasn’t detecting anything different after I updated the field to be a PK in the table.

MikeDE: I have tried marking it as read only and flagging it as a PK in Scriptcase. So far I haven’t had any luck. In fact, I’ve doubled checked just about every attribute for this field and form against another form that IS working and they are pretty much identical. I appreciate your suggestion, but I don’t feel like I should have to hack a fix like this together. However, I might have to, but I’d much rather the software work like it is intended to.

It’s agitating that Scriptcase exhibits this sort of unpredictable behavior in projects. Is it so much to ask for this development software to behave like it is supposed to? lol :smiley:

#5

Can you reproduce the problem in another app? If so can you explain the steps doen in making the application where this bug occurs?

#6

I have tried creating another form for the same table. The issue persists. Literally the only step I need to take to reproduce the problem is create a form with that table. For whatever reason, the PK id field is editable.

At this point I’ve already wasted plenty of time. I’ll have to resort to hacking a fix together because Scriptcase isn’t doing what it is supposed to.

#7

Well just after making the app it is supposed to be editable but I assume you mean it still is after putting it on read-only and/or as a label field?

Anyways what version of SC are you running and what kind of form do you use? I.e. editable grid, etc.

#8

[QUOTE=catalyst;34125]
At this point I’ve already wasted plenty of time. I’ll have to resort to hacking a fix together because Scriptcase isn’t doing what it is supposed to.[/QUOTE]

finally :slight_smile: the button line :slight_smile: I told you loool just have new field, copy it from that field you want to make it as label, and hide the original, then you lose nothing as the new field is only in SC, not in db.

anyway still strange, if you had a time to reproduce in new app as hoihoi661 suggested then you can export the app the sql dump to know whats wrong, i guess you are overlooking something small either in db or in form/field settings

cheers

#9

[QUOTE=catalyst;34125]
At this point I’ve already wasted plenty of time. I’ll have to resort to hacking a fix together because Scriptcase isn’t doing what it is supposed to.[/QUOTE]

finally :slight_smile: the bottom line :slight_smile: I told you loool no worries thought, you can make the new copied field as sc field only, not db field and hide the db one.

anyway still strange, if you have a time to reproduce in new app as hoihoi661 suggested then you can export the app the sql dump to know whats wrong, i guess you are overlooking something small either in db or in form/field settings

cheers

#10

[QUOTE=catalyst;34122]I appreciate your suggestion, but I don’t feel like I should have to hack a fix like this together. However, I might have to, but I’d much rather the software work like it is intended to.
It’s agitating that Scriptcase exhibits this sort of unpredictable behavior in projects. Is it so much to ask for this development software to behave like it is supposed to? lol :D[/QUOTE]

This is the world of ScriptCase.
The most important knowledge that a ScriptCase developer gains is how to work around the broken things.
If everything worked the way it is supposed to, we wouldn’t have anything to complain about! :rolleyes:

Dave