FileMaker.
Also, the Office Suite replacements, NeoOffice, LibreOffice, have a database component.
The GUI part of a database is a “front end” user interface for implementing the CRUD (create, read, update, delete) functions at a user level.
While not quite mutually exclusive, they are different parts of a database system.
Learning SQL is best done from a Non-GUI approach. I find typing out the SQL code to create a query is now much simpler than using the Access query builder. It is also much more powerful.
There are some GUI workspace programs that allow you to visualize the schema and provide interfaces for creating the code such as the MySQL Workbench and the Navicat programs. Likely many others.
I’ve never seen a pure database “front end” development environment besides a full-blown IDE for developing any app, database or not.
It is either bundled in a database program such as Access or Filemaker, or the user interface is developed as a standalone component using some programming environment. You can use Access as a front end for a SQL Server database, but I’m not sure if you can do the same with FileMaker.
EDIT: I decided to search for such a component and found this article. It wraps up a lot of the workbench-type programs: http://www.databasejournal.com/features/mysql/article.php/3880961/Top-10-MySQL-G UI-Tools.htm
Not all have OS X versions.
I also was reminded that if you know Java, NetBeans or Eclipse can help make a user interface fairly simply.
And one final note, SQLite3 is bundled with OS X, so you can use it’s very basic functionality to learn the basic SQL syntax on the command line.
