03-02-2023, 10:46 PM
(03-02-2023, 07:12 PM)Balderdash Wrote: Is it just a flex that people are always trying to write up databases in QB64 rather than just use database tools to make and edit databases? If someone plans on putting some of this code out in a "production" environment, it might be well worth their time and give them some peace of mind to use something that's tried and true rather than being responsible for not only making the database, but also making all the code that maintains it.
But it's boring that way LOL, to some of us who are still trying to sharpen our programming skills, whether or not we get paid as programmers. At one time, it was fun using dBase until version 4 which wrecked the hard disks of the old IBM PC XT's some cheapskate college still insisted on. It was fun using this program I purchased, obviously created with Borland Pascal which had a nice GUI (was MS-DOS program in "SCREEN 0"). What a shame I couldn't go further with either after a few months. I couldn't even write a decent program in dBase language, while watching for long enough one of the computer science teachers doing it while working on the school roster. "Give me the dot," once he protested after he fixed something. LOL. (The interactive mode of dBase had the "dot" prompt.)
Programming in BASIC might be easier than programming for SQL, while most queries wouldn't be as complicated as it is usually with businesses everyday. I know next to nothing about what goes on in those transactions. What I know is that interpreted BASIC didn't have UDT's and therefore maligned for insisting on strings to hold numeric data for random access. That changed with QuickBASIC v4 I think, and the UDT's, it transformed what people thought about doing databases with a general-purpose programming language. It might have been better, however, if M$ went further with ISAM than VBDOS, or something else to encourage database programming to give SQL a run for its money.
Some people might protest that it might be great if QB64(PE) supported an object-oriented programming style, in order to have methods to operate on data, which looks sensible from the point of view of databases. But then getting fancy with polymorphism, templates and stuff like that isn't cool if somebody like this topic's starter desires to keep it fast and simple...