OK, so the SQL database is managed by some bespoke executable which launches a set of bespoke front ends, apparently developed using "Component One True DB Input" all of it written around 2002.
Component One apparently lives on as some developer tool.
https://www.grapecity.com/componentone/ … ut-activexIf it won't all run on 10 in compatibility mode then we're going to need to find someone competent to deal with it.
I still don't see how converting it all to Access isn't a total cop-out.
Also on a cursory inspection it does have some major flaws, like using the same fields for different data depending on what you're doing - one set gets written over the other - and updated data also gets written straight over old data when both should be stored (I could be wrong, its not crystal clear).
Furthermore some simple changes, to names in drop-down lists, can't easily be changed.
Probably going to need to get someone competent to deal with it really.