May 20, 200223 yr I have a db which has a welders form that is used to qualified a welder for two processes. I have combined two fields to create a unique ID for each process. The fields combined are the welders id number and the process (ex. 3605FCAW).I have written a script using the set field command that creates separate records for each process in another db to store the data. This works find except that sometimes the form is used for only one process. When only one process is used, the second unique field will only have the welders id (ex.3605). As this number is only enter once in the form, this creates another record in the db since there is no reord in the second db with just the welders id. I tried formatting the second unique field with the "isempty command" for the field to be blank. When the sript button is activated, FM pops-up a message stating that the script cannot be run until the second unique ID has a valid value. The relationship is defined on the unique id. Is there a way around this messenage Thanks
May 20, 200223 yr One method I see is you can remove the Not Empty validation from the second process field definition and you can auto-enter a value in there like XXXX. Then use your script to validate the value in the second process field If [secondProcess <> "XXXX"] (Then create your record) Else (End the script) Hope this helps.
Create an account or sign in to comment