3 ms·
My Internet claim to fame was writing a program to get people off of FoxPro to PostgreSQL: https://github.com/kstrauser/pgdbf https://github.com/kstrauser/pgdbf
by kstrauser 4y ago
My Internet claim to fame was writing a program to get people off of FoxPro to PostgreSQL: https://github.com/kstrauser/pgdbf https://github.com/kstrauser/pgdbf
FoxPro was nifty in many ways, but nightmarish outside the “single person running the app with the database on their local hard drive” setup. The moment you tried to put the database files on a file share (which is how you used it as a network DB), it was a world of locking pain. And a fun fact: the client libraries were single threaded to the point that you could only run one query at a time per machine. If you had 2 apps running at once, only one of them could be querying at any given time.
- As_You_Wish 4y agoNo.....there were commands that could be given that made it all run fine. That was 20+ years ago so I forget what it was.
- jiggawatts 4y agoIt's staggeringly difficult to even just back it up safely if it is in use 24/7. We had some customers that made their FoxPro app "too critical" to the business, which very rapidly becomes an untenable nightmare with no way out.
- blihp 4y agoThe default behavior made it multi-user unfriendly. A lot of that likely came from trying to remain dBase compatible and beginner friendly. It was actually one of the better (behaved and performing) multi-user DOS and early Windows databases I used that wasn't based on a client/server architecture. It was up to the developer to take care to avoid unnecessary locking. For example, you could open databases in read only mode, avoid locking when browsing via 'browse nomodify', don't lock the database until you actually needed to do your CRUD work etc. If you migrated apps to utilize SQL and other 'modern' (at the time) FoxPro features instead of the legacy FoxBase/dBase syntax much of this was taken care of for you. I had production databases with up to 100 concurrent users before the overhead of the locking mechanism really started to be a problem. (which back in the NetWare days was more than enough for many mid-sized business applications) Just by way of comparison, I saw lots of 'what the hell were they thinking?' multi-user MS Access deployments starting in the late 90's that were even worse... without the ability to mitigate the way FoxPro apps could. That said, of course client/server databases still scaled better, farther and easier.
- kstrauser 4y agoThat all jibes with my experience. It was in a weird place where if you developed new apps with it using all the best practices, it was probably fine. If you started with the typical single-user app and scaled it up by accretion rather than by design, it ended up being a total mess. But if you were the kind of dev team that was likely to do it the right way, you were likely to pick something client/server instead of FoxPro in the first place.
- jamal-kumar 4y agoI didn't get to try your tool, but after much wrangling with other stuff I ended up using this perl script (Ignore the fact that it has .php as the extension): http://www.burtonsys.com/download/dbf2csv.php http://www.burtonsys.com/download/dbf2csv.php Makes sense a format made in the same decade as this programming language would be the best tool for the job for me at the time, and if you're trying to export the data into anything other than postgres if need be.