Jim,
The advantage of the trigger(s) is that you have a chance to catch the culprit, whereas with a setting change, the problem could continue unmitigated.
Mike
------------------------------
Mike Street
Technical Support Engineer
Rocket Internal - All Brands
------------------------------
Original Message:
Sent: 06-20-2023 13:43
From: J Edwards
Subject: suppression of null record keys
Thanks Mike
------------------------------
J Edwards
IT Manager
Plimpton & Hills
Original Message:
Sent: 06-20-2023 12:49
From: Mike Street
Subject: suppression of null record keys
Jim,
There is no such setting.
A trigger would be your best option here.
Mike
------------------------------
Mike Street
Technical Support Engineer
Rocket Internal - All Brands
Original Message:
Sent: 06-20-2023 12:35
From: J Edwards
Subject: suppression of null record keys
Is there an environment variable or some config setting in jBASE that will prevent a programmer from attempting to write a record with a null record key? I would prefer this work globally and not based on a particular file. This system has a lot of very old code that has probably gone through several conversion prior to jBASE. I am aware I could put a trigger on the file, but I'm finding this issue across multiple files and would like to resolve it quickly. We're currently running jBASE 5.7 but will soon be upgrading to 5.8. Thanks.
------------------------------
J Edwards
IT Manager
Plimpton & Hills
------------------------------