BUG: Wizards Create Invalid Column Names for QueryDef JoinLast reviewed: July 31, 1997Article ID: Q139996 |
The information in this article applies to:
SYMPTOMSIf you use AppWizard or ClassWizard to create a MFC DAO recordset based on a predefined query (QueryDef) that joins tables that contain columns with identical names, the application generates an exception when it attempts to open the recordset. The exception indicates that:
'[table.column]' isn't a valid parameter name.where table and column correspond to actual table and column names in your database.
CAUSEThe exception is thrown due to the incorrect manner in which the wizards add delimiting brackets to the standard table_name.column_name references in your CDaoRecordset-derived class's DoFieldExchange. The wizards generate the following syntax:
[table.column]The correct syntax is:
[table].[column] RESOLUTIONYou must manually modify the CDaoRecordset-derived class's DoFieldExchange to correct those column references that use the incorrect syntax. Follow this procedure:
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
REFERENCESThe complete text of the following article in included in this article for your convenience: ********************* Beginning of Included Article ********************* ARTICLE-ID: Q139997 TITLE : FIX: "Item not found in this collection" with MFC DAO JoinThe information in this article applies to:
SYMPTOMSWhen you try to modify a record in an MFC DAO application that uses a recordset based on a join and that was created by AppWizard or ClassWizard, the application may throw an exception on the update. Specifically, the exception indicates:
Item not found in this collection. CAUSEWhen the wizards generate references to columns that have names that appear in multiple tables of the join, the wizards will precede the column name with the name of the table as a qualifier. Both the table name qualifier and column name are enclosed in brackets in the DFX functions of the CDaoRecordset-derived class's DoFieldExchange. For example:
[Table].[Column]The presence of the brackets combined with the use of the table name qualifier causes the search for the specified field in the collection of fields maintained by the database engine to fail. Note that the presence of brackets around unqualified column names does not interfere with the field name search and is thus acceptable. This explains why some fields will be updatable while attempts to update others throws the exception; the updatable fields are likely unique and therefore unqualified.
RESOLUTIONTo work around this problem, use one of the following two techniques depending on the names of the affected tables and columns (the ones for which table qualifiers are necessary).
If Table and Column Names Contain No SpacesRemove the brackets that enclose the table and column names. The resulting reference should be of this form:
Table.Column If Table and/or Column Names Contain SpacesDon't remove the bracket delimiters or your application will throw an exception that indicates:
Syntax error in query expression 'table name.column name'.Instead, you must override one of the existing overloads of the virtual function CDaoRecordset::SetFieldValue() as follows (assuming your CDaoRecordset is named CMyDaoRecordset):
void CMyDaoRecordset::SetFieldValue(LPCTSTR lpszName, const COleVariant& varValue) { CString strNewName(lpszName); StripBrackets(strNewName, strNewName.GetBuffer(0)); strNewName.ReleaseBuffer(); CDaoRecordset::SetFieldValue(strNewName, varValue); }This override uses the StripBrackets member function of CDaoRecordset to remove the offending brackets and allows the search for the field in the field collection to succeed. NOTE: You can easily add this override to your application by using the Visual C++ ClassView Add Member Function command. Please refer to the online documentation and Help files for more details about this command.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug was corrected in Visual C++ 4.1. ********************* End of Included Article *********************
|
Additional query words: MfcDAO
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |