03-03-2023, 07:11 AM
I agree with one thing. If the programmer is familiar with SQL, then go for it. If he/she is better at programming in SQL than in BASIC or some other general-purpose language then I agree with Balderdash, just go for it instead of bothering with a different language. Otherwise, learning SQL, when someone (like me) knows the most about BASIC dialects is another learning curve for somebody at least 50 years old. It should have been mentioned earlier. I'm not against SQL or any other programming method of doing things, especially about data storage and management. But I resist it because I'm not familiar with it. I could possibly sit down right now with M$ Visual Studio and use Visual Basic for some simple programs.
Possibly, because I also resist OOP LOL but it's one of my tendencies. I tried, I really tried to practice with Freebasic and like the ability to overload subprograms and functions but there was a time where I had to raise my hand and say, "Forget it!" For the same reason I had to abandon OOP in Turbo Pascal v5.5 and v6 which made me sad. I remember the day I bought Turbo Pascal v6 which came in a couple of 5-1/4-inch floppy disks. A few months later became disgusted with Turbo C++ with its syntax-coloring, and sometime later Turbo Pascal v7 was out which made my purchased copy look dull only because I couldn't use it effectively enough.
Possibly, because I also resist OOP LOL but it's one of my tendencies. I tried, I really tried to practice with Freebasic and like the ability to overload subprograms and functions but there was a time where I had to raise my hand and say, "Forget it!" For the same reason I had to abandon OOP in Turbo Pascal v5.5 and v6 which made me sad. I remember the day I bought Turbo Pascal v6 which came in a couple of 5-1/4-inch floppy disks. A few months later became disgusted with Turbo C++ with its syntax-coloring, and sometime later Turbo Pascal v7 was out which made my purchased copy look dull only because I couldn't use it effectively enough.