Window to Table — export lists from any Windows program to Excel

Window to Table — export lists from any Windows program to Excel

The data is on screen but there is no export button? This tool reads tables and lists straight out of another application´s window and saves them as CSV for Excel. It only reads — it never types or changes anything.

HONEST: WHAT IT READS AND WHAT IT DOES NOT

This is the part worth knowing before you buy.

READS WELL: old business software built with MFC, VB6 or Delphi using a standard table; Windows management consoles — Services, Registry Editor, Disk Management; pretty much anything that looks like Windows 2000.

DOES NOT READ: WinUI and WPF, which includes new Windows dialogs — Task Manager on Windows 11 was rewritten and has no classic list inside; Qt, used by a lot of engineering software; Java Swing, common in banking and factory systems; Electron and anything browser-based; games, they draw everything themselves.

If a program paints its table itself instead of using a standard Windows control, there is nothing to read — not with any tool of this kind.

You can find out whether it fits your case in a minute: open your window, run the tool, pick the window. Either you get a CSV, or it tells you plainly that there is no classic list there and prints the full list of window elements with their class names. No guessing.

The archive holds two builds: OknoVTablicu64.exe for 64-bit programs and OknoVTablicu32.exe for 32-bit ones. Reading another program´s list only works from a process of the same architecture. If you run the wrong one, the tool tells you which one you need. Old business software is very often 32-bit.

Nothing to install: .NET Framework ships with Windows 10 and 11.

Additional information:

An old warehouse management system. A supplier´s price list. An internal database that’s twenty years old. You see a perfect 5,000-row table on your screen—but there’s no export function. Usually, the next step involves manual copying or taking screenshots. "Okno v Tablicu" (Window to Table) reads such a table directly from the application window and saves it to a file that opens in Excel with a simple double-click.

HOW IT WORKS

1. Displays a list of open windows—you select the one you need.
2. Locates all data-containing elements within that window: tables, trees, simple lists, and drop-down lists. It reports the row count for each.
3. Exports the selected data, including column headers.
4. Saves the file as CSV (UTF-8 with BOM and a `sep=;` line)—Excel opens it immediately, without the import wizard and without garbled Cyrillic characters.

The program is READ-ONLY. It does not input data, click buttons, or modify anything in your application. It is neither an auto-clicker nor an input automation tool.

SCHEDULED EXECUTION

It supports command-line arguments and return codes, allowing you to set it up in Windows Task Scheduler to receive a fresh export every morning:
OknoVTablicu64.exe --window=Price --out=C:\data\price.csv --all

WHAT´S IN THE ARCHIVE

• Two ready-to-use programs: 32-bit and 64-bit (you must use the version matching the target application´s architecture—this is a Windows limitation; the program will detect the source´s architecture and tell you which version to run).

• User guide: covers all arguments, return codes, and troubleshooting for complex cases.

SUPPORTED ELEMENTS

Standard Windows controls: SysListView32 (report tables and lists), SysTreeView32 (trees), ListBox, ComboBox. This covers the vast majority of industry-specific programs written before the era of "fancy" interfaces—precisely the ones that lack an export function.

WHAT THE PROGRAM CAN´T DO (AND WHY)

If an application renders a table itself—using Delphi (TStringGrid), Qt, Java, WPF, or a browser engine—there are no distinct Windows rows; it is just a single canvas. The program recognizes these cases and states so explicitly, rather than pretending there is no data.

You can test it with your specific program before buying: just send me the name and, if possible, a screenshot of the window containing the table, and I’ll give you an honest answer about whether it will work.

VERIFIED

The Windows data structures have been verified via byte-level testing—separately for 32-bit and 64-bit systems—covering 26 offset checks; a single-byte error would result in garbled text. There are also 12 checks for CSV generation, covering the escaping of semicolons, quotation marks, and line breaks, as well as BOM handling and irregular row lengths.

REQUIREMENTS

Windows 7 or later. .NET Framework 4 (already included in the OS).