This is awesome. Loved the training video as well.
It’s kind of cool to see people putting in the effort to learn 30 commands and becoming masters of their own destiny. I guess it’s the same sense of mastery that Excel users have today.
Hopefully someone more learned than myself about modern database programming will chime in. I'm not sure what current system offers both the database and development features in such a seamless package. That said, on the Mastodon post for this article, I was told, "Learning dBASE isn't for naught" and was directed to https://xharbour.org/ as a modern dBASE/Clipper implementation. (haven't had a chance to try it yet, personally)
>> The prompt starts at the first field and <RETURN> (not <TAB> !) moves to the next.
This is hilarious to me, because times have certainly changed.
When we first started shipping Windows software the big complaint from users was the use of Tab to switch fields, while Return triggered the default button (usually Save or Close).
The change, for users used to DOS was painful - not least when capturing numbers as the numeric key pad has Enter not Tab.
Software developers either stood firm, convincing customers to learn Tab, or caved and aliased the Enter key to the Tab key. Even today I still find that option here and there in Software that's been around a while...
Author here, and thanks for reading. I'm glad to hear stories from a developer POV about those days. It's interesting uncovering subtle interface changes as I investigate various applications. It makes sense to me to not use Return for fields, especially when fields could gradually accommodate longer and longer blocks of text. Being able to naturally type multiple paragraphs, say for a "Notes" field in a database, would make sense.
Yes, it makes sense when viewed like that, and was probably a necessary change.
DOS chose Enter though because in those days mist data capture was numbers. Lots and lots of numbers. Data capturers could track the left hand down the column (so keeping place on yhe paper) any type with the right. Enter is right there in the keypad so only one hand needed.
Switching to Tab means 2 hands needed on the keyboard, so difficult to keep track on the paper.
Typically also, on DOS screens there was very little multi-line entry. Addresses were multiple entry fields, and so on. Tab was pretty much not used (outside of word processing).
If I went back now, to design the standard keyboard, I'd add dedicated "Next" and "Previous" buttons on the numeric keypad. No need for Enter there.
Since someone else posted my article instead of me, I felt compelled to clarify who I am. Just trying to navigate social media waters to the best of my ability.
It’s kind of cool to see people putting in the effort to learn 30 commands and becoming masters of their own destiny. I guess it’s the same sense of mastery that Excel users have today.
What’s the dBase II/III equivalent today?
Hopefully someone more learned than myself about modern database programming will chime in. I'm not sure what current system offers both the database and development features in such a seamless package. That said, on the Mastodon post for this article, I was told, "Learning dBASE isn't for naught" and was directed to https://xharbour.org/ as a modern dBASE/Clipper implementation. (haven't had a chance to try it yet, personally)
I had memories of Foxpro and Clipper on my mind, when I found myself in this rabbit hole.
This is hilarious to me, because times have certainly changed.
When we first started shipping Windows software the big complaint from users was the use of Tab to switch fields, while Return triggered the default button (usually Save or Close).
The change, for users used to DOS was painful - not least when capturing numbers as the numeric key pad has Enter not Tab.
Software developers either stood firm, convincing customers to learn Tab, or caved and aliased the Enter key to the Tab key. Even today I still find that option here and there in Software that's been around a while...
DOS chose Enter though because in those days mist data capture was numbers. Lots and lots of numbers. Data capturers could track the left hand down the column (so keeping place on yhe paper) any type with the right. Enter is right there in the keypad so only one hand needed.
Switching to Tab means 2 hands needed on the keyboard, so difficult to keep track on the paper.
Typically also, on DOS screens there was very little multi-line entry. Addresses were multiple entry fields, and so on. Tab was pretty much not used (outside of word processing).
If I went back now, to design the standard keyboard, I'd add dedicated "Next" and "Previous" buttons on the numeric keypad. No need for Enter there.
But that's design with a lot of hindsight...