AI SMART HUB· Guide
Everyday use · Chapter 8/14

Result reports: SQLite, quick view and Excel export

Every report line from your scripts is collected in a safe data store. See failed accounts, common errors, results by day, one account's history, and export to Excel.

2 min read · updated Nov 20, 2026

Why a SQLite report store

Writing CSV/Excel files from many threads at once easily corrupts files or loses lines, and the tool cannot write while Excel has the file open. So the tool also collects every report into one database file gpm_data.db (SQLite, built in, nothing to install). The old CSV files are still written alongside as before.

The store collects 3 kinds:

  1. Script reports (the Write line to csv file / Write csv report commands): each old CSV file = 1 "report name".
  2. Swap results.
  3. The money-rotation ledger.

Quick view

Run & settings → More tools → Open the SQLite report viewer (or double-click xem_bao_cao.bat). Pick a report name, then a question:

QuestionAnswer
Failed accountsAccounts whose last result was an error, with details
OK accountsAccounts that finished
Common errorsGroups identical errors and counts accounts
By dayOK / error lines per day
Find account / walletThe full history of one account or wallet address across every report

Export to Excel

  • Press Export in the viewer, or run xuat_bao_cao.bat.
  • Command line (inside the tool folder):
python gpm_db.py                         show a summary
python gpm_db.py xuat tat_ca             everything into 1 Excel file, one sheet per report
python gpm_db.py xuat bao_cao_swap --tu 2026-11-01 --den 2026-11-12
python gpm_db.py nhap ket_qua_cu.csv     import an old CSV file into the store (once per file)
💡 Using Claude Desktop? Type "summarize this week's reports, which accounts failed most" and the AI reads this store directly through the MCP gateway.
© 2026 AI Smart Hub · Automate Intelligence. Elevate Possibilities. · Updated Nov 20, 2026
Home · Blog · Terms · Zalo · Telegram