Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Trigger failed
Message
From
14/07/2005 09:59:31
 
 
To
14/07/2005 08:48:08
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Title:
Miscellaneous
Thread ID:
01032390
Message ID:
01032615
Views:
15
This message has been marked as the solution to the initial question of the thread.
>>>Hi,
>>>
>>>I have a following configuration in "Referencial Integrity Builder"
>>>
>>>ParentTable - ChildTable - Update  - Delete   - Insert - ParentTag - ChildTag
>>>Vara        - Conta      - Cascade - Restrict - Ignore - var_cod   - con_varcod
>>>
>>>
>>>When I try to insert data in Conta table with 0 to the field con_varcod I get the message "Trigger failed in Conta"
>>>
>>>Insert into Conta (Con_Cod, Con_VarCod, Con_Nome) values (1, 0, 'Test') && Trigger failed in Conta
>>>
>>>
>>>It´s bug in "Referencial Integrity Builder" ?
>>
>>One bug that brought me grief in the past is that sometimes the wrong table is selected. Perhaps you have another table, whose name starts with "vara", and that happens to be open? This is a situation that should be avoided.
>>
>>The debugger might help to see what is going on.
>
>Are one error in the StoredProcedure generated by DBC. The error occours in this line.
>
unlock record pnParentRec in lcParentWkArea
>If I change this line to
>
unlock record pnParentRec in (lcParentWkArea)
>It work correctly.
>
>I think that the Referencial Integrity Editor is a builder with opened code like the ReportOutput.APP. So I want to make this correction in possible builder of Referencial Integrity Editor. What is the builder to Referencial Integrity Editor ?


In XSource have the folder Builders where exists the RIBuildr.PJT
In the RIBuildr project I change the lines
unlock record pnParentRec in lcParentWkArea
To
unlock record pnParentRec in (lcParentWkArea)
Compile generating the RIBuildr.APP, copy this to the Wizards folder in the VFP Instal Folder and it resolve my problem.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform