Preventing Primary Key from Changing

[[email protected]]

I looked thru the posts, but did not see anything specifically about disallowing a primary key from changing.

I have an inventory file that I set to modal so that a "Change Button" has to be selected for changing anything on the record. However, I noticed that the change button will allow for the primary key (part number) to be changed as well. Is there some easy condition that I can set that prevents the primary key from changing unless the form is in the add or delete mode??

Thanks,

Ryland

[Stan Mathews]

Re: Preventing Primary Key from Changing

Set the skip in the data entry field rules to true.

[[email protected]]

Re: Preventing Primary Key from Changing

Stan,

How do I unset the rule if there is a new record ro be added. The skip works, but unfortunately works on entering a new record. I assume that there must be a cas or if command that I can put into the dictionary..

[Mendy]

Re: Preventing Primary Key from Changing

Not sure what type of form you are using. If you have fields on form you could initially set your part number field as disabled. This would allow changes in other fields. Then you could use action scripting to make two buttons, one for enable object and other disable object. Just a thought. Lots of different ways to do same thing.

[Tom Cone Jr]

Re: Preventing Primary Key from Changing

Ryland, many would argue against using a part number as a primary key. They'd be worried about non-uniqueness. Each primary key must uniquely identify each specific record, or it's not a primary key. Maybe your part numbers are unique by definition, but many are not. -- tom

[[email protected]]

Re: Preventing Primary Key from Changing

Hi Tom,

Yes in this instance (since I'm dealing in gov apps) it has to be the part number as it is references throughput the Military. I think if I just identify if I'm in an add or delete mode, then I can prevent any field changes to the part number. Just not sure what function tells me what mode I'm in.

Ryland

[Tbaker]

Re: Preventing Primary Key from Changing

Ryland

Here is a link to the web help on mode.get()

http://support.alphasoftware.com/alp...Mode_Get().htm

Tom Baker

[[email protected]]

Re: Preventing Primary Key from Changing

Thanks Tom,

Also I found another way to cheat this on. When I select the "Change Button", I placed a disable object in the action script, and conversely, wgen I add a new record I enable the object. Seems to work so far, but I guess my concern is what happens on queries and browes....meaning that if someone goes in for a browse after a change, what efferct it will have on the record. Hopefully none...... Ryland

[Tim Kiebert]

Re: Preventing Primary Key from Changing

Stan,

How do I unset the rule if there is a new record ro be added. The skip works, but unfortunately works on entering a new record. I assume that there must be a cas or if command that I can put into the dictionary..

Use this for the skip rule.

TABLE.CURRENT().MODE_GET() < 2

But you better be sure to enter the value correct before saving the new record. May be an extra warning message in the Onsave event or Ondepart of the field in the form.

Alternatively you could have a password protected dialog box that runs some xbasic code to fix the value if necessary. But you would want to check any table that use that value as a foreign key and update them as well.

[[email protected]]

Re: Preventing Primary Key from Changing

Tim,

Just wanted to get back to you. The mode change < 2 works perfect. Once my Master files are built (usually by an import), this accidental re-write over the primary record will not happen.

Thanks,

Ryland