PRB: "Argument Not Optional" Error Using DAO 3.5Last reviewed: October 16, 1997Article ID: Q168206 |
The information in this article applies to:
SYMPTOMSAfter porting a Visual Basic 4.0 program that is written using DAO 3.0 (Data Access Objects) to DAO 3.5, the error message:
"Argument Not Optional"will occur on the Update, Movelast, and CommitTrans methods. This does not happen in Visual Basic 5.0.
CAUSEIn DAO 3.0, the methods listed above do not use optional arguments. They do use optional arguments in DAO 3.5. This is a problem caused by adding the Typed Optional Parameter feature to OLE Automation. Only newer Automation controllers such as Visual Basic 5.0 are going to understand this. Visual Basic 4.0 can accept optional parameters only if they are of the Variant data type. The optional arguments for the methods listed above are not Variant so it doesn't recognize them as optional.
RESOLUTIONThere are three options for this problem:
STATUSThis behavior is by design. Microsoft does not support the use of DAO 3.5 in Visual Basic 4.0. It is recommended that DAO 3.0 or lower be used.
MORE INFORMATIONFor information on how to use the methods mentioned above, refer to the Visual Basic online help. Keywords : APrgDataAcc VB4WIN vb5all VBKBDAO kberrmsg kbprb Technology : kbole Version : 4.0 5.0 Platform : WINDOWS Issue type : kbprb |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |