If the user can enter data that can create a dup error I’ll add code to check and help him fix it by identifying the exact problem field and selecting it.
E.g. we only allow an SSN to be entered once, and same if they use the time keeping Clock Number:
IF DUPLICATE(Emp:KeySSN) THEN
Message('SSN is already entered on another record....')
ELSIF Emp:ClockNo AND DUPLICATE(Emp:KeyClockNo) THEN
Message('Clock Number is already entered on another record....')
The question of which field is causing the duplicate doesn’t really make sense.
Instead the question becomes which KEY(s) are duplicates for this record, is what does make sense.
The closest you get is to determine that a given key is considered a duplicate, and then display the components of that key, or simply skip showing the internals to your users, and instead make it more user friendly.
That said, you might find the two FileManager.GetFieldName( … ) methods to be interesting.
On a side note, you talked about Access:File.GetError.ToString() not compiling.
I think it’s a valid assumption that Access:File is a FileManager
The prototype for GetError is FileManager.GetError PROCEDURE(),SIGNED
Clarion does not support stringing methods together like Object.MethodA().MethodB()
I’ve recall this syntax being called “dotting through” but I cannot find this definition online.
Typically for this syntax to work, MethodA needs to return a class (or interface) so everything to the left of the .MethodB() is an expression which results in an object which has a MethodB() method.
FileManager.GetError() returns a ,SIGNED so dotting through wasn’t going to work.
What’s more is I can’t find a .ToString method in Libscr\win
except for in SystemString and in CWInt.INT
Lastly even if Clarion did support dotting through, then you’d need to change .GetError.ToString() to .GetError().ToString()
The KEY has the Duplicate but it is caused by the component fields. If it is a Form you want to tell the User as directly as possible which Entry in the Form is causing the problem and select it for him so he can can fix it. It is possible the Form Entry USE() is not the field but used to calculate it. I have tried to think of a generic way to code that but it seems too hard when the goal is to make a super obvious message to the user.
Blue you can check DUPLICATE(File) which checks all keys. I will sometimes use that as an ELSE in case a key is added not handled by the code e.g.
IF DUPLICATE(Transaction) THEN
IF DUPLICATE(Tran:KeyID) THEN
LogIt('ID dup ....')
ELSIF DUPLICATE(Tran:KeyReference) THEN
LogIt('Reference dup ....')
LogIt('Transaction File has unexpected Dup key I do not handle ....')