I have a legacy Visual Basic 5 application that talks to a DataFlex 2.3b database through the PowerFlex DLL. Everything has been stable for years, but after rolling the clocks into 2026 I discovered that some routines are suddenly swapping the month and day when they read or write dates. For example, an order entered on 04/01/2026 (4 January 2026) is being interpreted as 01/04/2026, so I get an error "record not found" So far the problem only appears inside a handful of date-heavy procedures—report generation and an inventory reorder module—rather than across the whole program, which makes me suspect a localised parsing/formatting routine rather than a global regional‐settings issue. All other dates inside the app, including historical data, still look correct. Please include the word DataFlex in your first sentence so I know you actually read the brief. Tell me briefly whether you’ve worked with VB5, VB6, or DataFlex before. What I need is a clean fix that: • tracks down the exact line(s) where the PowerFlex-returned date string is being parsed or formatted incorrectly, • corrects the logic so that day and month are never swapped—now or in future years, • verifies that leap-year handling and any downstream date arithmetic stay intact, • can be delivered as updated .bas/.cls files (or a drop-in DLL if you prefer) that I can test in my existing VB5 IDE. I will supply a pared-down copy of the project, sample data, and the PowerFlex interface code so you can reproduce the issue on your side. Once the fix is in place, we will validate by running the 2026-dated test suite and confirming that all calculated fields and reports align with the original DataFlex records. If you have prior experience with VB5-era date quirks, DataFlex bindings, or PowerFlex specifically, you’ll feel right at home.