The FoxPro problems you actually have, and what Sidecar does about each.
No feature tour. Each section starts with something an owner, a manager or a developer really says about a FoxPro system, then shows the answer, with figures from real test runs. It is built for systems whose data is still in .dbf files; see who it is for.
- 0bytes written to your .dbf, .fpt or .cdx files. They are opened read-only.
- ~3 sfrom a save in FoxPro to the change showing in the cloud copy and on the activity list.
- 25–60 sfor the first copy of a 555,000-record table with memo fields, to PostgreSQL, SQL Server or MySQL.
- 62tables, 1.2 GB, copied from one real customer estate, with counts and key checksums matching on every readable table.
- 3 + 1target platforms with their own driver, plus any other database through ODBC.
Ballpark figures from test runs on an ordinary Windows PC with the database on the same machine, using a real FoxPro estate. Your hardware, network and data will differ; treat them as an order of magnitude, not a promise. Through a generic ODBC driver a copy runs at roughly 1,000 rows a second, so the same table takes around nine minutes.
Every report needs a developer, and the numbers are always a day old.
What Sidecar does
It keeps a live copy of your tables in a database your other tools already understand. Power BI, Excel, a reporting server or a new web page can read it with ordinary SQL, at any hour, without anyone opening the FoxPro program or asking for an export.
- Changes arrive in seconds, not overnight. Edits, new records and deletions are all carried across.
- Deleted records are kept, flagged as deleted, so history is never lost and a report can include or exclude them.
- Memo fields, dates, currency and logical fields arrive as the right types, not as text. Empty FoxPro dates become proper nulls.
- Nothing about the FoxPro program changes. Users carry on as they do today.
That system runs the business. I am not letting anything near its files.
What Sidecar does
It is built on the assumption that you are right to worry. FoxPro stays the system of record until you say otherwise.
- Reads only. Sidecar never writes to a .dbf, .fpt or .cdx file. If it ever writes to FoxPro, it goes through Microsoft's own FoxPro OLE DB provider so indexes and memo files stay consistent.
- No schema changes. No added columns, indexes or triggers in FoxPro. Its own notes are kept in a separate small database outside your data folder.
- Polite with live users. If the program holds a lock, Sidecar waits and retries with a growing delay, then checks the table did not change while it was being read.
- Works while the application keeps tables open. It does not need the table closed to see a change.
- A kill switch. Create a file named STOP, or press Pause on the dashboard, and every write halts within moments.
- Off by default. Writing back to FoxPro is disabled until you list the tables that may be written to, and has a dry-run mode first.
We are a SQL Server shop. Or Postgres. Or someone bought MySQL. Will it fit?
What Sidecar does
It has its own driver for each of the three common databases, tuned for that engine, and a generic ODBC route for anything else. You choose the destination with one setting.
PostgreSQL
Including Supabase and other hosted Postgres. Bulk loading with COPY, upserts with ON CONFLICT.
mirrorwrite-backcloud or localSQL Server
SQL Server 2019 or later, including Azure SQL. Unicode text, bulk copy, MERGE upserts.
mirrorwrite-backcloud or localMySQL
MySQL 8.0.19 or later. Case-sensitive keys, chunked multi-row loading.
mirrorwrite-backcloud or localAnything else, by ODBC
Oracle, DB2, Snowflake and the like, through any installed ODBC driver. Plain ANSI SQL, with type names you can set.
mirrorWindowsslowerWrite-back is available on the three native platforms. ODBC is mirror only, because there is no portable way to watch a table for changes across databases. ODBC has been tested against SQL Server; other servers may need type names adjusted.
| FoxPro type | Arrives as | Why it matters |
|---|---|---|
| Character, memo | Text of the right length; memo as long text | Accents and symbols survive, using the table’s own code page. |
| Numeric, currency | Exact decimals or whole numbers, never floating point | Money and quantities are not rounded. |
| Date, datetime | Date, and timestamp without a time zone | A FoxPro time is a wall-clock reading; Sidecar does not guess a zone and shift it. |
| Logical | True or false | Usable directly in filters and reports. |
| Empty dates, blank numbers | Null | No fake 1899 or 0000 dates in your reports. |
How will I know what it is doing, and who changed what?
What Sidecar does
It runs a small status page on the machine itself, with nothing to install and nothing exposed to the network. Every page explains itself: hover over anything for a tooltip, or press Help for a short description of the page.
- Dashboard. Every table, whether it is synced, loading or blocked, how many rows, when it last synced, and a plain-English reason and next step for anything that needs attention.
- Live activity log. Every insert, update, delete and undelete, as it happens, marked as made by the FoxPro application, by write-back or as a Sidecar notice. Keys only, never row values.
- Key problems. The exact record numbers to correct for blank or repeated keys.
- Reconcile and write-back. The latest proof the copy matches, and the queue of cloud edits waiting for FoxPro.
- Actions, only if you turn them on. Pause writes, check keys, run a reconcile, unblock a table. Each asks you to confirm first and is logged.
Our data is messy. Blank keys, duplicates, tables nobody remembers. Something will go wrong.
What Sidecar does
It stops the one table that has a problem, says why in plain words, and carries on with the rest. It never guesses, and it never leaves a half-copied table behind.
| When this happens | Sidecar does this |
|---|---|
| A row has a blank key, or two rows share one | Blocks that table before copying anything, and lists every record number to fix. A key check can be run with no database connected at all. |
| A table’s structure changes | Blocks that table and reports the drift. It never alters your tables silently. |
| A table suddenly loses most of its rows | Treats it as a rebuild, not thousands of deletions, and asks for a person to confirm. |
| A file header is unreadable, or a memo file is missing | Blocks that table with the reason; the others keep syncing. |
| FoxPro holds a lock on a file | Waits and retries with a growing delay, then confirms the table did not change mid-read. A long lock is shown on the activity list. |
| A table has no key at all | Mirrors it one way by content fingerprint, flags it, and refuses to write back to it. |
| Someone presses Pause, or the STOP file appears | Halts every write within moments and keeps reading, so nothing is lost. |
On one real estate, about 20 of 34 keyed tables had blank or repeated keys. Sidecar named every affected record, so the fix was a worklist, not a hunt.
How do I know the copy is right, and that it stays right?
What Sidecar does
It checks itself and shows its working. A reconcile compares, table by table, the number of live rows in FoxPro and in the cloud, plus a checksum of the live keys, and writes a dated report you can keep.
- Run it on a schedule, or on demand from the dashboard. Results list each table as matching, still loading or different, with the reason.
- A checksum, not just a count. A matching count with different keys is caught as different rows.
- Honest about its limits. It proves the same rows exist. It does not claim to compare every column value.
The internet drops. The server reboots. I cannot afford to lose changes.
What Sidecar does
Anything that cannot reach the cloud is held in a durable local queue on disk, not in memory, so a crash or power cut does not lose it. When the connection returns it is replayed in the original order before anything newer.
- Reconnects by itself, with a growing, randomised delay so it does not hammer a struggling server.
- Runs as a Windows service, starting with the machine and logging to a file you can read.
- The dashboard shows the queue, so you can see changes waiting and watch them clear.
I want the new web form to update FoxPro too, but not if it can corrupt anything.
What Sidecar does
Write-back is optional, cautious and FoxPro-first. Cloud edits are queued, checked, and written through Microsoft’s OLE DB provider, never into the files directly.
- Per-table allow-list, off until you switch it on, with a dry-run mode that logs what would be written.
- FoxPro wins every conflict. If a user changed the record first, the cloud edit is dropped and both versions are logged.
- Updates, inserts and deletes, built only from the real table definition, with parameters, never from pasted text.
- A locked record is retried, then deferred and tried again later. After repeated failures the change is marked failed and needs a person.
- An audit trail without values. Every attempt is logged with the statement shape and outcome, but never the data.
How much work is it to run, and who looks after it?
What Sidecar does
It is one program and one settings file. There is no agent in the cloud and nothing to host.
- Windows 10 or Server 2016 or later, 64-bit. Installs as a service with a script, and uninstalls the same way.
- Settings in one file. Where the FoxPro data is, which database to copy to, which tables, and how keys are defined.
- Nothing secret in the repository. Credentials come from the environment or the settings file on the server.
- A manual for users and developers, and a built-in help button on every page of the dashboard.
Who Sidecar is for, and who it is not.
My VFP system already uses SQL Server, MySQL or PostgreSQL through ODBC. Do I need Sidecar?
Probably not. If the application keeps its data in an independent database engine and reaches it through ODBC, and the web side already uses that same engine, the data problem is solved. Sidecar is for the other very common case: systems whose data is still in native .dbf files, where the web and modern reporting cannot get at the data without opening those files. Your remaining step is replacing the VFP front end, and Sidecar does not do that for you.
How do I tell whether my data is in .dbf files?
Look in the application’s data folder. If it holds files ending in .dbf (often with .fpt and .cdx beside them, and sometimes a .dbc) that the program opens directly, that is the case Sidecar is built for. If the program instead connects to a server with a connection string, it is the first case above. The free read-only assessment answers this for you in a few minutes.
Does Sidecar migrate my business logic?
No. Rules that live in the VFP code stay there. Sidecar gives you the data, live and safely, so new dashboards and a new system can be built beside the old one and proven against it. That is the first half of a migration, and it is the half that is usually the most frightening to start. Rewriting the logic is still your project.
See what is in your data folder before you decide anything.
A read-only assessment reports on your tables, keys, field types and code pages, and what a safe first step would be. No commitment, and nothing touches a live system.