Archive

How to use Application.FindFile in the xlwings API way

The FindFile method of the Application object in Excel is a powerful tool for programmatically opening the “Open” dialog box, allowing users to search for and select a file to open within the Excel application interface. This method mimics the action of clicking “File” > “Open” in the Excel ribbon, providing a user-interactive way to locate files without hardcoding file paths in your scripts. In xlwings, which provides a clean Pythonic interface to automate Excel, you can access this Excel method through the api property of the main App or Book objects, giving you direct access to the underlying Excel object model.

Functionality:
The primary function of FindFile is to display the standard Open dialog box. It returns a Boolean value: True if a file is successfully opened, and False if the dialog is canceled by the user. This method is particularly useful in scenarios where the script needs to prompt the user to select a file dynamically, such as in data import routines or when working with files that may change location.

Syntax in xlwings:
In xlwings, you call this method via the api property of an Application object. The typical syntax is:

result = xw.apps[0].api.FindFile()

Or, if you have a specific app instance:

app = xw.App()
result = app.api.FindFile()

The method does not take any parameters. The return value result is a Boolean indicating success (True) or cancellation (False).

Parameters:
FindFile has no parameters in Excel VBA, and this is directly mirrored in xlwings. The method relies entirely on user interaction within the displayed dialog.

Example Usage:
Here is a practical example using xlwings to open the Open dialog and handle the user’s selection:

import xlwings as xw

# Start or connect to Excel
app = xw.App(visible=True) # Ensure Excel is visible to see the dialog

# Display the Open dialog
file_opened = app.api.FindFile()

# Check the result
if file_opened:
    print("A file was successfully opened by the user.")
    # You can now interact with the opened workbook, e.g., get its name
active_book = app.books.active
    print(f"Opened workbook: {active_book.name}")
else:
    print("The Open dialog was canceled by the user.")

# Keep the app open or close as needed
# app.quit()

How to use Application.ExecuteExcel4Macro in the xlwings API way

The ExecuteExcel4Macro member of the Application object in Excel’s object model provides a way to run Excel 4.0 macro functions, which are legacy commands from older versions of Excel. While modern Excel primarily uses VBA, these functions can still be useful for specific tasks that are not directly supported by newer APIs, such as certain financial or engineering calculations. In xlwings, this functionality is accessed through the api property, which exposes the underlying Excel object model, allowing Python scripts to interact with Excel in a manner similar to VBA.

The syntax for calling ExecuteExcel4Macro via xlwings is straightforward. First, you need to obtain the Application object from an xlwings App or Book instance. Then, you can invoke the method. The method takes a single string argument, String, which represents the Excel 4.0 macro function you want to execute. This string should be formatted exactly as it would be in Excel 4.0, including any required arguments. For example, a common function is GET.CELL, which retrieves information about a cell. The parameter is provided as a plain string, and you must ensure it is correctly quoted and concatenated if variables are involved. There is no return value specification in the syntax itself; the output depends on the macro function called.

Here is a basic example that demonstrates how to use ExecuteExcel4Macro with xlwings to get the full path of the active workbook, using the Excel 4.0 function GET.DOCUMENT(1):

import xlwings as xw

# Connect to the active Excel instance
app = xw.apps.active

# Execute the Excel 4.0 macro function to get the full path
full_path = app.api.ExecuteExcel4Macro("GET.DOCUMENT(1)")

print(f"Full path of active workbook: {full_path}")

Another example involves retrieving a specific cell’s value using GET.CELL. This can be useful for getting properties like the cell’s format or formula. In this case, you need to construct a reference string:

import xlwings as xw

# Connect to the active workbook and sheet
wb = xw.books.active
sheet = wb.sheets.active

# Define the cell address, e.g., A1
cell_address = "A1"

# Execute GET.CELL(6, A1) to get the formula in the cell (6 is the type_num for formula)
# Note: The reference must be provided as an R1C1-style reference or a named range
formula_result = wb.app.api.ExecuteExcel4Macro(f'GET.CELL(6, {cell_address})')

print(f"Formula in {cell_address}: {formula_result}")

How to use Application.Evaluate in the xlwings API way

The Application.Evaluate method in Excel is a powerful tool for converting a Microsoft Excel name or a formula string into an actual value or a reference object. In xlwings, this functionality is exposed through the api property of an App or Book object, allowing you to leverage Excel’s calculation engine directly from Python. This is particularly useful for evaluating complex formulas that are easier to express in Excel’s native syntax than to replicate in Python code, or for retrieving the value of a defined name.

The syntax in xlwings follows the pattern of accessing the underlying Excel object model. To call Evaluate, you first obtain the Excel Application object via the api property. The method takes a single string argument, which is the name or formula to be evaluated.

Syntax:

app.api.Evaluate(Name)

• app: This is your xlwings App object (e.g., xlwings.App() or xw.apps.active).
• .api: This property provides direct access to the pywin32 or appscript COM object, enabling calls to the raw Excel VBA object model.
• .Evaluate: The method being called.
• Name (String, Required): A formula, a defined name, or a reference (as a string) that you want Excel to evaluate. This must be provided in the locale of the Excel application or in A1-style notation. For example, "SUM(A1:B10)", "MyNamedRange", or "Sheet1!$C$5".

The method returns the result of the evaluated formula. This can be a simple data type (like a number, string, or boolean), an xlwings.Range object (if the name evaluates to a range reference), or an error.

Code Examples:

1. Evaluating a Mathematical Formula:
   This calculates a formula string and returns the numeric result.

import xlwings as xw

app = xw.App(visible=False)
wb = app.books.add()
# Place values in cells
wb.sheets[0].range('A1').value = 10
wb.sheets[0].range('A2').value = 20

# Use Evaluate to compute the sum
result = app.api.Evaluate("SUM(A1:A2)")
print(result) # Output: 30.0
wb.close()
app.quit()

2. Evaluating a Defined Name:
   This retrieves the value or reference associated with a name defined in the workbook.

import xlwings as xw

app = xw.App(visible=False)
wb = app.books.add()
# Define a name for a range
wb.api.Names.Add(Name="MyData", RefersTo="=Sheet1!$A$1:$A$5")
# Put values into the named range
wb.sheets['Sheet1'].range('A1:A5').value = [[1], [2], [3], [4], [5]]

# Evaluate the defined name to get its value (the array)
name_result = app.api.Evaluate("MyData")
print(list(name_result)) # Output: [1.0, 2.0, 3.0, 4.0, 5.0]
wb.close()
app.quit()

3. Evaluating a Formula that Returns a Range Object:
   This is useful for obtaining an xlwings Range object from a string reference.

import xlwings as xw

app = xw.App(visible=True)
wb = app.books.add()
ws = wb.sheets[0]
ws.range('B2').value = "Hello World"

# Evaluate returns a Range COM object, which xlwings wraps.
# The xlwings Range constructor can handle this COM object.
range_ref = app.api.Evaluate("Sheet1!B2")
xl_range = xw.Range(range_ref) # Wrap it in xlwings Range
print(xl_range.value) # Output: Hello World
print(xl_range.address) # Output: $B$2
# wb.close() and app.quit() omitted for an interactive example.

How to use Application.DoubleClick in the xlwings API way

In the Excel object model, the Application.DoubleClick method is a powerful feature that simulates a double-click action on the active cell in Excel. This action can trigger various Excel behaviors, such as entering cell edit mode, opening a cell for formula editing, or activating specific cell features like data validation lists. In xlwings, this functionality is accessible through the api property, which provides direct access to the underlying Excel COM object. This allows Python scripts to automate user interactions that typically require manual double-clicks, enhancing automation workflows in data processing and analysis.

The syntax for using DoubleClick in xlwings is straightforward, as it is called as a method without any parameters. Since it operates on the active cell, it requires that a cell is selected or active in the Excel application. In xlwings, you typically access this through the Application object, which represents the Excel instance. The method is invoked as follows:

app.api.DoubleClick()

Here, app refers to the xlwings App instance connected to Excel. The api property exposes the native Excel COM interface, allowing direct calls to methods like DoubleClick. This method does not take any arguments; it simply performs the double-click action on whatever cell is currently active in Excel. It is important to note that the effectiveness of this method depends on the context—for example, if the active cell contains a formula, double-clicking might place the cursor in the formula bar for editing, while in a cell with data validation, it might open a drop-down list.

To use Application.DoubleClick in xlwings, you must first ensure an Excel application is running and a workbook is open. Below are practical code examples demonstrating its usage:

Example 1: Basic double-click to edit a cell. This example opens Excel, selects a specific cell, and simulates a double-click to enter edit mode.

import xlwings as xw

# Connect to the active Excel instance or start a new one
app = xw.apps.active if xw.apps.active else xw.App()
wb = app.books.active if app.books else app.books.add()
ws = wb.sheets.active

# Select cell A1 and activate it
ws.range('A1').select()
app.api.DoubleClick() # Simulate double-click on A1
# This may allow editing of the cell content in Excel

Example 2: Using double-click in a loop to process multiple cells. This can be useful for automating tasks like checking data validation or triggering macros tied to cell events.

import xlwings as xw

app = xw.apps.active
if app:
    ws = app.books.active.sheets.active
    for cell in ws.range('B1:B5'):
        cell.select() # Make each cell active
        app.api.DoubleClick() # Double-click to interact with each cell
        # Add a pause or other operations as needed, e.g., app.wait(1)

Example 3: Combining with other xlwings features to log actions. This example double-clicks on a cell and then updates another cell with a timestamp.

import xlwings as xw
from datetime import datetime

app = xw.apps.active
if app:
    ws = app.books.active.sheets.active
    target_cell = ws.range('C3')
    target_cell.select()
    app.api.DoubleClick() # Trigger double-click on C3
    # Record the action in cell D3
    ws.range('D3').value = f'Double-clicked at {datetime.now().strftime("%H:%M:%S")}'

How to use Application.DisplayXMLSourcePane in the xlwings API way

The DisplayXMLSourcePane member of the Application object in Excel is a property that controls the visibility of the XML Source task pane. This pane is used when working with XML maps in Excel, allowing users to view and manage XML elements mapped to cells or ranges in a workbook. It is particularly useful for developers and advanced users who handle XML data integration, enabling them to see the structure of XML data and its mappings directly within the Excel interface. In xlwings, this property can be accessed and manipulated to programmatically show or hide the XML Source pane, enhancing automation in workflows involving XML data processing.

In terms of syntax, the DisplayXMLSourcePane property is accessed through the Application object in xlwings. The xlwings API provides a Pythonic way to interact with Excel’s object model. The property is a boolean value, where True indicates that the XML Source pane is visible, and False indicates it is hidden. The xlwings call format is straightforward: you reference the Application object and set or get the DisplayXMLSourcePane property. For example, to retrieve the current state, you use app.api.DisplayXMLSourcePane, and to change it, you assign a boolean value like app.api.DisplayXMLSourcePane = True. Note that in xlwings, the api attribute is used to access the underlying Excel object model properties and methods directly, ensuring compatibility with Excel’s native functionality.

Here are some code examples demonstrating the use of DisplayXMLSourcePane with xlwings. First, ensure you have xlwings installed and an Excel instance running. You can use the following snippets in a Python script or interactive environment. In the first example, we check if the XML Source pane is currently visible and print its status:

import xlwings as xw

# Connect to the active Excel instance
app = xw.apps.active

# Get the current state of the DisplayXMLSourcePane property
is_visible = app.api.DisplayXMLSourcePane
print(f"The XML Source pane is visible: {is_visible}")

To show the XML Source pane, set the property to True:

# Show the XML Source pane
app.api.DisplayXMLSourcePane = True
print("XML Source pane is now visible.")

To hide it, set the property to False:

# Hide the XML Source pane
app.api.DisplayXMLSourcePane = False
print("XML Source pane is now hidden.")

You can also toggle the visibility based on its current state. This is useful in automation scripts where you might need to ensure the pane is visible before performing XML-related operations:

# Toggle the visibility of the XML Source pane
current_state = app.api.DisplayXMLSourcePane
app.api.DisplayXMLSourcePane = not current_state
print(f"Toggled XML Source pane visibility to: {not current_state}")

How to use Application.DeleteCustomList in the xlwings API way

The DeleteCustomList member of the Application object in Excel VBA is used to remove a previously defined custom autofill or sort list. In xlwings, which provides a Pythonic interface to Excel’s object model, this functionality can be accessed through the api property of an App or Book object, which exposes the underlying VBA object model. This is particularly useful for managing custom lists programmatically, such as cleaning up temporary lists or resetting configurations in automated Excel tasks.

Functionality
The primary purpose of DeleteCustomList is to delete a custom list that has been added to Excel. Custom lists are often used for custom sorting orders or to define autofill sequences (e.g., a list of department names or project stages). Deleting a list can help maintain a clean Excel environment, especially when lists are created dynamically during a script’s execution and are no longer needed afterward.

Syntax in xlwings
In xlwings, you call this method via the Application object obtained from an xlwings App instance. The syntax is:

app.api.DeleteCustomList(ListNum)

• app: This is an xlwings App object, representing the Excel application.
• api: This property provides direct access to the VBA Application object.
• DeleteCustomList: The method being called.
• ListNum: A required parameter of type Integer. It specifies the index number of the custom list to delete. The index corresponds to the position of the list in Excel’s custom lists collection, where custom lists are numbered sequentially starting from 1. Note that Excel’s built-in lists (like days and months) cannot be deleted and are not included in this count; the indexing applies only to user-defined custom lists.

To determine the correct ListNum for a specific list, you may need to retrieve it from Excel’s list collection. This can be done by using the GetCustomListNum method or by iterating through custom lists if you know the list’s contents. However, DeleteCustomList itself does not identify lists by name; it requires the numerical index.

Code Example
Below is an example demonstrating how to use DeleteCustomList in xlwings. This script adds a custom list, confirms its addition, and then deletes it. Note that error handling is important because attempting to delete a non-existent list or an out-of-range index will raise a com error.

import xlwings as xw

# Start or connect to Excel application
app = xw.App(visible=False) # Set visible=True to see Excel interface

try:
    # First, add a custom list for demonstration
    custom_list = ["North", "South", "East", "West"]
    app.api.AddCustomList(ListArray=custom_list)
    print("Custom list added successfully.")

    # Assume we want to delete the most recently added list.
    # In a real scenario, you might need to find the index dynamically.
    # Here, we use index 1, assuming it's the first user-defined list.
    # Note: This might fail if other custom lists exist.
    list_num = 1 # Index for the custom list to delete
    app.api.DeleteCustomList(ListNum=list_num)
    print(f"Custom list at index {list_num} deleted.")

except Exception as e:
    print(f"An error occurred: {e}")

finally:
    # Close Excel
    app.quit()

In this example, list_num is hard-coded as 1 for simplicity. In practice, to reliably delete a specific list, you might first use GetCustomListNum to find its index based on the list array, or maintain a record of list indices when creating them. The AddCustomList method returns the index of the newly created list, which can be stored for later deletion. For instance:

# When adding a list, store the returned index
new_list_index = app.api.AddCustomList(ListArray=custom_list)
# Later, delete using the stored index
app.api.DeleteCustomList(ListNum=new_list_index)

How to use Application.DDETerminate in the xlwings API way

The DDETerminate member of the Application object in Excel is used to manually close a specific Dynamic Data Exchange (DDE) channel that was previously established using the DDEInitiate method. DDE is an older inter-process communication protocol that allows Windows applications to exchange data in real-time. While modern applications often use more advanced technologies like COM or Office Add-ins, DDE is still occasionally used for legacy integrations. The DDETerminate method ensures that DDE channels are properly closed, freeing up system resources and preventing potential memory leaks or application instability. In xlwings, which provides a Pythonic interface to Excel’s COM automation, you can access this method through the Application object to manage DDE channels programmatically.

Syntax in xlwings:
The xlwings API mirrors the Excel Object Model, allowing direct calls to Excel methods. For DDETerminate, the syntax is:

app.api.DDETerminate(Channel)

• Channel (required, Long): An integer that specifies the DDE channel number to close. This channel number is returned by the DDEInitiate method when a DDE conversation is started. It uniquely identifies the open connection between Excel and another application.

To use this, you typically first initiate a DDE channel with DDEInitiate, perform data exchanges, and then terminate it. The parameter must be a valid, open channel number; passing an invalid number may result in a runtime error. Note that DDE channels can also close automatically when the workbook is closed, but explicit termination is recommended for clean resource management.

Example:
Suppose you have a DDE link to another application, such as a financial data server. Below is an xlwings code example that demonstrates initiating and terminating a DDE channel. This example assumes you have an existing Excel application instance and a workbook open.

import xlwings as xw

# Connect to the active Excel instance
app = xw.apps.active

# Initiate a DDE channel to an application (e.g., a hypothetical server "FINANCE" with topic "DATA")
# In practice, replace "FINANCE" and "DATA" with valid application and topic names for your DDE server.
try:
    channel = app.api.DDEInitiate("FINANCE", "DATA")
    print(f"DDE channel initiated with channel number: {channel}")

    # Perform DDE operations here, such as requesting data using    app.api.DDERequest or app.api.DDEPoke
    # Example: request data from item "PRICE" on the channel
    # data = app.api.DDERequest(channel, "PRICE")
    # print(f"Received data: {data}")

    # Terminate the DDE channel explicitly when done
    app.api.DDETerminate(channel)
    print("DDE channel terminated successfully.")
except Exception as e:
    print(f"An error occurred: {e}")

How to use Application.DDERequest in the xlwings API way

The DDERequest method of the Application object in Excel is a legacy function used to retrieve data from an external application via Dynamic Data Exchange (DDE). This method allows Excel to act as a DDE client, requesting specific information from a DDE server application. While DDE is an older technology largely superseded by more modern methods like COM or various APIs, understanding DDERequest can be crucial for maintaining or interfacing with legacy systems that still rely on DDE communication channels. In the context of xlwings, which provides a Pythonic way to automate Excel, you can access this method through the Application object.

Functionality
The primary function of DDERequest is to establish a DDE conversation with a server application and request a specific data item. It is used to fetch real-time or static data from programs that support DDE, such as some financial data feeds, scientific instruments, or older database systems. The method initiates a request for a particular item within an established DDE channel.

Syntax
In xlwings, the DDERequest method is accessed via the Application object. The general syntax is as follows:

app.application.DDERequest(Channel, Item)

• Channel (Required): A Long integer that represents the channel number returned by a previous DDEInitiate call. This channel identifies an open DDE conversation with a server application.
• Item (Required): A String that specifies the data item being requested from the DDE server. The format and meaning of this string are defined by the server application. It often resembles a cell reference (e.g., “R1C1”) or a named range specific to the server.

Parameters and Usage
The method requires a pre-established DDE channel. Typically, you use the DDEInitiate method first to open a channel to a specific server and topic. The Item parameter is entirely dependent on the DDE server’s protocol. Common examples include requesting specific stock prices, instrument readings, or database fields. The method returns a Variant containing the requested data, which could be a number, string, or array.

Code Example
The following xlwings code example demonstrates how to use DDERequest to request data from a hypothetical DDE server. The example assumes a server application named “MyServer” with a topic “Prices”, and requests the item “StockXYZ”.

import xlwings as xw

# Connect to the active Excel instance or start a new one
app = xw.apps.active

# First, initiate a DDE channel (this is typically done via Excel's DDEInitiate method).
# Note: xlwings does not have a direct wrapper for DDEInitiate, so we use the underlying API.
# This requires the channel number from a successful DDEInitiate call.
# For demonstration, we assume channel number 5 is already open.
channel_number = 5 # This would come from a prior DDEInitiate call.

# Use DDERequest to get data for the item "StockXYZ"
try:
    requested_data = app.api.DDERequest(Channel=channel_number, Item="StockXYZ")
    print(f"Data received via DDE: {requested_data}")
except Exception as e:
    print(f"DDERequest failed: {e}")

# In a real-world scenario, you would also close the channel using DDETerminate.
# app.api.DDETerminate(Channel=channel_number)

How to use Application.DDEPoke in the xlwings API way

The DDEPoke method in Excel’s object model is a feature of the Application object that allows sending data from Excel to another application via Dynamic Data Exchange (DDE). This method is useful for automating communication with other programs that support DDE, enabling Excel to act as a client that pushes data into a server application. In xlwings, this functionality can be accessed through the api property, which provides direct access to the underlying Excel object model. While DDE is an older technology largely replaced by more modern methods like COM or APIs, understanding DDEPoke can be beneficial for maintaining legacy systems or interacting with specific software that still relies on DDE channels.

The syntax for calling DDEPoke via xlwings follows the Excel object model structure. In xlwings, you typically use the app object to represent the Excel application, and then access the DDEPoke method through its api property. The method signature in Excel VBA is Application.DDEPoke(Channel, Item, Data), where Channel is a Long integer representing the DDE channel number established with another application, Item is a String specifying the item in the DDE conversation (e.g., a cell reference or topic), and Data is the value to send. In xlwings, this translates to app.api.DDEPoke(Channel, Item, Data). The parameters must be provided in the correct order: first the channel, then the item, and finally the data to poke. It’s important to note that a DDE channel must already be opened using DDEInitiate before DDEPoke can be used, as the channel number is returned by that initiation call. The data parameter can be a string, number, or array, depending on what the receiving application expects.

Here is an example of using DDEPoke with xlwings to send data from Excel to another application. Suppose you have a DDE channel opened with a hypothetical program like a financial terminal, and you want to update a specific item with a value. First, ensure you have xlwings installed and import it. Then, you can write a script that starts Excel, initiates a DDE channel, and uses DDEPoke to send data. Below is a code instance:

import xlwings as xw

# Start or connect to an Excel application
app = xw.App(visible=True) # Set visible=False for background operation

# Assume a DDE channel has been established earlier, e.g., via DDEInitiate
# In practice, you would use app.api.DDEInitiate(app_name, topic) to get a channel
# For this example, let's pretend channel number 1 is already open
channel = 1 # This should be the actual channel number from DDEInitiate
item = "R1C1" # Item to poke, e.g., a cell reference in the DDE conversation
data = "Hello from Excel via DDE" # Data to send

# Use DDEPoke to send the data
try:
    app.api.DDEPoke(channel, item, data)
    print("Data poked successfully.")
except Exception as e:
    print(f"Error in DDEPoke: {e}")

# Close the Excel application if needed
app.quit()

In this example, replace channel with the actual channel number obtained from DDEInitiate. The item parameter might vary based on the DDE server’s requirements—it could be a range like “R1C1” for a cell or a specific command string. The data is sent as a string, but it could be numeric if the application expects it. Always handle errors with try-except blocks, as DDE operations can fail if the channel is closed or the server is unresponsive. This method is particularly useful in scenarios where you need to automate data feeds to legacy systems without modern API support, but for new projects, consider using more robust integration methods like REST APIs or direct database connections.

How to use Application.DDEInitiate in the xlwings API way

The DDEInitiate method of the Application object in Excel is a legacy function used to initiate a Dynamic Data Exchange (DDE) conversation with another application. DDE is an older interprocess communication protocol that allows Windows applications to exchange data in real-time. While largely superseded by more modern technologies like COM or .NET, understanding DDEInitiate can be crucial for maintaining legacy automation systems or interacting with applications that still primarily support DDE.

In the context of xlwings, which provides a Pythonic wrapper around the Excel Object Model via COM, you can access this method through the app object, which represents the Excel Application. The xlwings API call mirrors the VBA syntax closely.

Functionality:
The primary function is to open a DDE channel to another application. Once established, this channel can be used to send commands or request data using other DDE methods like DDEExecute or DDERequest. It returns a channel number, which is an integer identifier for the opened conversation. This number must be used in subsequent DDE operations and eventually closed with DDETerminate.

Syntax in xlwings:

channel_number = app.api.DDEInitiate(App, Topic)

• Parameters:
• App (Required, String): The name of the application to communicate with. This is typically the executable name without the .exe extension (e.g., “WinWord” for Microsoft Word).
• Topic (Required, String): The topic of the conversation. This often refers to a document name or a system topic. For many applications, a common system topic is “System”.

Code Example:
The following xlwings script demonstrates initiating a DDE conversation with a hypothetical server application named “DataServer” on the “System” topic, performing a simple operation, and then properly terminating the channel.

import xlwings as xw

# Start Excel application (or connect to a running instance)
app = xw.App(visible=True) # Set visible=False for background operation

try:
    # Initiate a DDE conversation
    channel = app.api.DDEInitiate(App="DataServer", Topic="System")
    print(f"DDE Channel opened: {channel}")

    # Example: Execute a command on the server (e.g., request an update)
    # app.api.DDEExecute(channel, "[UpdateAll]")

    # Example: Request data from the server
    # data = app.api.DDERequest(channel, "CurrentData")

    # Always terminate the channel when done
    app.api.DDETerminate(channel)
    print("DDE Channel terminated.")

except Exception as e:
    print(f"An error occurred: {e}")
    # Ensure channel is terminated even on error (if it was opened)
    # In a robust script, you would check if 'channel' exists before calling DDETerminate.

# Close Excel
app.quit()

Important Notes:

1. DDE is a legacy, less secure protocol. Its availability and behavior depend heavily on the operating system and application settings. Modern versions of Windows may restrict DDE operations by default for security reasons.
2. The success of DDEInitiate depends entirely on the target application being running and configured to accept DDE conversations on the specified topic.
3. The xlwings .api property grants direct access to the underlying pywin32 COM object, allowing you to call methods like DDEInitiate that are not wrapped by a dedicated xlwings function. This is the standard approach for utilizing less common Excel Object Model members.
4. Always pair DDEInitiate with DDETerminate to properly close the channel and free system resources. Failing to do so can lead to memory leaks or unstable application states.
5. For most new development, exploring alternatives like a dedicated API, COM automation, or file-based exchange is strongly recommended over DDE.