You really have to decide whether any relations are needed. ListPro is possible, flat-file, it has a limit of about 30 fields to a file.
For heftier stuff, maybe there are discounts on older Filemakers but it might be hard to justify for a limited app.
I don't think it is that MYSQL etc are complicated per se, it is that:
1) they think in terms of server-client, which is unnecessary. Technically an app could probably do that transparently using local host giving a sort of equivalent to the .dbf .fp7 etc files. (experts, your comments ?)
I am curious if there is any real, innate difference. When a program like Alpha 5 runs on an MYSQL file instead of DBF or something else .. what is the actual difference in your puters functioning ? MYSQL is able to have relations and structures built-in, but it could also simply be used as flat file(s) with optionally simple index relationships, afaik (which presumably are some type of join). And does your program have to actually work through a server traffic cop ? Does anything prevent it from being simply accessed directly.
2) they have not built much in terms of Listpro and Filemaker type ease-of-use products, being more involved in small programs like Navicat "administration", thinking that you are concerned about a web-site in far-off cloud land. And trying to integrate with PHP and other web languages in fair to middling development tools that have no relevance to a local database.
What I may be saying is that the problem is more historical than structural. And programs like Filemaker and Alpha will possibly work directly on MYSQL (and maybe other similar databases).
Just throwing out some thoughts. This has puzzled me for awhile, since I have not done much in that SQL database realm.