Append error Violating Field Rules

[pk9]

I am appending records with same structure and field rules into cover01.dbf from cover02.dbf and I get a message stating "Records Violating Field Rules" for the number of records and nothing is appended.
I try to "View Violations" and I get warning "Could not find set '\Docume" and that is it.
Any clues greatly appreciated.
Peter

[Stan Mathews]

Re: Append error Violating Field Rules

My search for similar error reports leads me to believe you might have a problem with a lookup field rule during the append.

[pk9]

Re: Append error Violating Field Rules

Stan,
You are probably correct. Is there a way to globally turn on/off the field rules.
Thanks.

[pk9]

Re: Append error Violating Field Rules

I am able to append as follows:
Cover02.dbf (w/Field rules) to Cover05.dbf (w/o Field Rules)
or
Cover04.dbf (w/o Field rules) to Cover05.dbf (w/o Field Rules)

BUT if the source table has field rules it will not APPEND.

I checked all LOOKUPS for references that do not exists but they do.
Only the Issuedate fields are suspicious.
Peter

[robert]

Re: Append error Violating Field Rules

why not post copies of 1 and 2 with only a few pieces of data so everyone can look at the structure and field rules?

[pk9]

Re: Append error Violating Field Rules

Per Al Buchholz note regarding field rule deletion via Control Panel has helped in removing part of the violating field rules.
It seems that deleting field rule otherwise did not actually delete it.

See
http://msgboard.alphasoftware.com/al...+opening+rules

[Mike Wilson]

Re: Append error Violating Field Rules

Peter,
Yes you can change the field rules with a script. Here is a UDF I wrote to change the field rules for Entry type from autoincrement to user defined. It is a start for getting the lookup field rule adjusted. I'll look at it further when I get a chance.

FUNCTION FRFT_change AS C (tablename as C, fieldname as C, start_type as C, end_type as C)
	
'This function is used to changes the Field Rule Entry Type from Autoincrement to User Entry

DIM VMESS AS C
VMESS = "This function requires exclusive use of the table and cannot be run when others are accessing the database"

Ui_msg_box("FIELD RULE CHANGE MESSAGE",VMESS)

dim tablename as C
dim fieldname as C
dim start_type as C
dim end_type as C
dim vpre as C

vPre = "rul." +fieldname+".Data_type="

dim ptr as P

ptr = table.open(tablename,FILE_RW_EXCLUSIVE)
rul = ptr.rules_get()
rul.change_begin()
evaluate_template(vpre + s_quote(start_type))
rul.change_end()
ptr.close()

ptr = table.open(tablename,FILE_RW_EXCLUSIVE)
rul = ptr.rules_get()
rul.change_begin()
evaluate_template(vpre + s_quote(end_type))
rul.change_end()
ptr.close()

END FUNCTION

[pk9]

Re: Append error Violating Field Rules

Mike,
Thanks that script is very helpful.
I appreciate it given that A5 has something like 10,000 command according to Ira, it is easy to not find what you are looking for.
Peter

[csda1]

Re: Append error Violating Field Rules

Hi Mike,

Peter,
Yes you can change the field rules with a script. Here is a UDF I wrote to change the field rules for Entry type from autoincrement to user defined. It is a start for getting the lookup field rule adjusted. I'll look at it further when I get a chance.

"This function is used to changes the Field Rule Entry Type from Autoincrement to User Entry"

I wonder if this is really true? If the same table pointer used by whatever is being done is used, then the field rules are in memory of the client system. If modified in the memory part, then I would guess that is what would be used. Thus, you may not have to modify the actual field rules that are stored, and might not have to use the table exclusively.

You will have to try is while a form is opened on the same table or a 2nd computer to prove whether this concept reallly works.