Named Arguments Are Not Supported with DAO

RESOLUTION

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. To work around this behavior, use positional arguments instead of named arguments.

In a Visual Basic macro, when you call a Subroutine or Function, you can supply arguments positionally, in the order in which they appear in the definition of the procedure. Alternatively, you can supply the arguments by name without regard to position. However, with DAO properties and methods, Microsoft recommends that you use only positional arguments.

Example of the Problem

The DAO 3.5 OpenDatabase method uses the following syntax:

   Set <database> = OpenDatabase(dbname, options, readonly, connect)
				

If you use the OpenDatabase method by supplying named arguments in the macro, you may receive one of the errors described in this article. For example, when you run the following macro, the compile error "Named Argument Not Found" appears:

   Set DB = _
      OpenDatabase(dbname:= "C:\My Documents\DB1.MDB", readonly: = True)

Example of the Resolution

To correct the problem, use positional arguments. To do this, supply the arguments for the method in the correct position, where each argument is delimited by a comma, as shown in the following example:

   Set DB = OpenDatabase("C:\My Documents\DB1.MDB", , True)