It was boxed software that, when going to a computer/office store as a child in the mid-1990s, you wanted your parents to buy because it had a fox on the cover and in the name without actually knowing what it did.
Besides being a DB with forms, reports, etc as already mentioned by others - its significance was huge as it was the peak of an era where small/single developers could deliver business solutions by knowing a single tool, and people with domain knowledge could write their own solutions.
Since then everything became much more complex - networking, security, GUIs, web development, deployment, etc.
A tool and language to write apps where you could write "Select * from customers" in the command window and get results right there in a browse table, beautifully
Yes, they bought it. But they didn’t buy it and stab it in the heart. They developed it for several years.
A primary bit of tech that came out of the purchase was the core DB engine. They reworked this into what became the Jet engine. The Jet engine was the core of Access.
Access was in many ways a next generation of FoxPro. They both went after the same niche of desktop and file server DB applications. But FoxPro carried the legacy of its dBase roots, FoxBase was basically “better dBase”, but had to appeal to and be familiar to dBase developers.
Access had no heritage like that to hold it back, and was a better citizen in the VB/Office/OLE/COM world. It was also more SQL first even though it kept things like DBF files as first class citizens.
It was boxed software that, when going to a computer/office store as a child in the mid-1990s, you wanted your parents to buy because it had a fox on the cover and in the name without actually knowing what it did.
Simply speaking from experience.
An IDE, form designer, language, runtime, and database engine.
People used it to write business applications. Like Microsoft Access, or Visual Basic.
It started as a competitor to dBase II/III called FoxBase, and then Microsoft bought it.
Besides being a DB with forms, reports, etc as already mentioned by others - its significance was huge as it was the peak of an era where small/single developers could deliver business solutions by knowing a single tool, and people with domain knowledge could write their own solutions.
Since then everything became much more complex - networking, security, GUIs, web development, deployment, etc.
Original - FoxPro: https://en.wikipedia.org/wiki/FoxPro
Successor - Visual FoxPro: https://en.wikipedia.org/wiki/Visual_FoxPro
A tool and language to write apps where you could write "Select * from customers" in the command window and get results right there in a browse table, beautifully
Not a single language nowadays can do that
a database program, IIRC it was a program not by microsoft but MS bought it and killed it off
Yes, they bought it. But they didn’t buy it and stab it in the heart. They developed it for several years.
A primary bit of tech that came out of the purchase was the core DB engine. They reworked this into what became the Jet engine. The Jet engine was the core of Access.
Access was in many ways a next generation of FoxPro. They both went after the same niche of desktop and file server DB applications. But FoxPro carried the legacy of its dBase roots, FoxBase was basically “better dBase”, but had to appeal to and be familiar to dBase developers.
Access had no heritage like that to hold it back, and was a better citizen in the VB/Office/OLE/COM world. It was also more SQL first even though it kept things like DBF files as first class citizens.