﻿<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>StrataFrame Forum » StrataFrame Application Framework - V1 » Business Objects and Data Access (How do I?)  » Exception when saving a parent/child with more than one field in primary key</title><generator>InstantForum 2017-1 Final</generator><description>StrataFrame Forum</description><link>http://forum.strataframe.net/</link><webMaster>StrataFrame Forum</webMaster><lastBuildDate>Tue, 09 Jun 2026 16:02:05 GMT</lastBuildDate><ttl>20</ttl><item><title>Exception when saving a parent/child with more than one field in primary key</title><link>http://forum.strataframe.net/FindPost3908.aspx</link><description>I have a screen with two business objects on it in a parent/child relationship.&amp;nbsp; The parent object has two fields in its primary key and the child has three.&amp;nbsp; The PrimaryKeyIsAutoIncremented property is set to false for both objects.&amp;nbsp; Whenever I try to save, the BusinessLayer.PushDataToChildren method throws a BusisnessLayerException.&amp;nbsp; The description is "The PrimaryKeyIsAutoIncremented property on business object [] cannot be True because the PrimaryKeyField property contains more than one field.".&amp;nbsp; I took a look at this method and it looks to me like the problem is that the check that determines whether or not this exception should be thrown looks only at the number of fields in the primary key and ignores the state of the PrimaryKeyIsAutoIncremented property.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fran Parker.&lt;/P&gt;&lt;P&gt;MaxQ Technologies, Inc.</description><pubDate>Fri, 27 Oct 2006 10:51:20 GMT</pubDate><dc:creator>fparker</dc:creator></item><item><title>RE: Exception when saving a parent/child with more than one field in primary key</title><link>http://forum.strataframe.net/FindPost3910.aspx</link><description>Yes, that was a bug, the Save() method was properly checking the PrimaryKeyIsAutoIncremented property before calling the PushDataToChildren() method, however, the SaveByForm was not checking the same value before calling it.&lt;/P&gt;&lt;P&gt;The resolution will be in the build we are releasing later today.&amp;nbsp; Thanks.</description><pubDate>Fri, 27 Oct 2006 10:51:20 GMT</pubDate><dc:creator>StrataFrame Team</dc:creator></item></channel></rss>