Data Access Worldwide Knowledge Base
Article Text
QUESTION:
The explanation for this error in the help is:
This error should not normally occur. It is a dataset legacy feature that should not be in use, and support of this feature has been removed in Visual DataFlex 11.0 due to Non Numeric Multiple Column Row Identifier (NNMCRI or RowId) changes. However, it is possible that this error can occur if a dataset is improperly used.
What does "improperly used" mean?
ANSWER:
This is a new error added to 11.0. It is catching a condition that always has always been a bug but it used to go unreported.
This happens when you try to perform a DDO action on a table that the DDO cannot reach in its structure. This can occur two ways: Either you are asking for a file that is not in the structure at all or you are asking for a child file within a parent.
I would guess that is the case, where you are trying to perform a find on a child within a parent DDO (e.g. Send request_find of MyParenttDDO MyChildFile ....). This is not supported -- you can find on parents from within a child but not the other way around.
Prior to Visual DataFlex 11.0, it would let you try this and there was no error when it ended up not really working. Now you get an error, so you can see it and correct it.
Contributed By:
John Tuohy
Company: Data Access Worldwide
Web Site: http://www.dataaccess.com
Web Links Related to this Article
DAW Knowledge Base article 2091: ERROR: "Invalid Use of Non-Main Table"
URL=http://www.dataaccess.com/KBPrint.asp?ArticleID=2091
Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2010 Data Access Corporation. All rights reserved.
| The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. |