Microsoft KB Archive/101318
Article ID: 101318
Article Last Modified on 6/13/2001
- Microsoft Access Distribution Kit 1.1
- Microsoft Access Developer's Toolkit 2.0
This article was previously published under Q101318
Advanced: Requires expert coding, interoperability, and multiuser skills.
Run-time applications developed with Microsoft Access have the same dynamic data exchange (DDE) server capabilities as applications in the retail version of Microsoft Access.
However, in order to communicate with a run-time application using DDE, you must use the name of the .MDB file, instead of "MSACCESS" when initiating a DDE conversation.
The following example demonstrates how to communicate with a run-time application developed with Microsoft Access:
- Start Microsoft Access and open the sample database NWIND.MDB.
- Choose the Macro button and select the Sample Autoexec macro.
- From the File menu, choose Rename. In the Macro Name box, type "Autoexec" (without the quotation marks), and then press ENTER.
- Quit Microsoft Access.
- From the File menu in Program Manager, choose Run.
- Type "c:\access\msarn110.exe nwind.mdb" (without the quotation marks), and then press ENTER.
- Start Microsoft Access, and create or open a database other than NWIND.MDB.
Create or open a module and add the following Access Basic function:
Option Explicit Function DDEWithNWIND () Dim chan chan = DDEInitiate("NWIND", "NWIND;TABLE Employees") MsgBox DDERequest(chan, "FirstRow") DDETerminate chan End Function
Note that the first argument specified in the DDEInitiate command, the application name, is "NWIND", which is the name of the .MDB file, and not "MSACCESS."
From the View menu, choose Immediate Window. Type the following line, and then press ENTER:
Note that a message box displays the first record from the Employees table in the NWIND.MDB database.
Additional query words: adk adt nxml
Keywords: kbhowto kbinterop KB101318