Feedback
Did this article resolve your question/issue?

   

Article

Pro2: Table update fails after Pro2 replication triggers added. Getting error (4461)

Information

 
TitlePro2: Table update fails after Pro2 replication triggers added. Getting error (4461)
URL Nametable-update-fails-after-pro2-replication-triggers-added-getting-error-4461
Article Number000133687
EnvironmentProduct: OpenEdge
Version: 4.6.x
OS: Windows
Other: Pro2
Question/Problem Description
Table update fails after Pro2 replication triggers added.  Getting error (4461)
Application keeps asking if the user wants to save the changes they just made.
 
Steps to ReproduceAdd Pro2 replication triggers to several new tables.
Clarifying Information
Error MessageWhen using character client session can see error:
Trigger for table <table> is executing <procedure>, which is compiled against a different logical database name. (4461)

This will often report this error message as well:
<program name> Database <dbname> not connected. (1006)
Defect/Enhancement Number
Cause
Trigger code is compiled with specific logical database name.
In the .pf file used to connect to the databases an incorrect logical database name was listed.
Resolution
The database name listed in the (1006) error should be used for the -ld parameter value.

Example:
mytest.r Database mydatabasename not connected. (1006)

Set the -ld value to mydatabasename.
Example:
-db sports2000
-ld mydatabasename
Workaround
Notes
Last Modified Date7/5/2018 1:21 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.