snowbdr
asked on
What is best between MSAccess, mysql or filemaker
I spent many years developing a robust database on MSAccess and now I have changed companies and need to start another. A lot has changed in the 11 years since I started working with databases, but I don't know anything other than Access. The database I need to build will be used entirely or primarily within our office with less than 6 users. It would be great if I could create a limited interface usable on my iphone, but this is not at all necessary.
Filemaker issues: The reports will get fairly complicated by pulling from more than 15 tables and I have heard that filemaker may have some limitations with that. I like to use comboboxes and listboxes a lot and I have heard filemaker has limited options with these.
mysql: Is there a front-end development program that is similar to Access or possibly easier to use? It seems like knowledge of php is necessary and I have heard it is fairly complicated. I do not have any other programming knowledge as I was self taught on MSAccess and learned necessary coding primarily from this site and other online resources.
Filemaker issues: The reports will get fairly complicated by pulling from more than 15 tables and I have heard that filemaker may have some limitations with that. I like to use comboboxes and listboxes a lot and I have heard filemaker has limited options with these.
mysql: Is there a front-end development program that is similar to Access or possibly easier to use? It seems like knowledge of php is necessary and I have heard it is fairly complicated. I do not have any other programming knowledge as I was self taught on MSAccess and learned necessary coding primarily from this site and other online resources.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Dave Baldwin
The common SQL databases (MySQL, MS SQL, PostgreSQL, and Oracle) are servers and they do not come with 'front ends' They all have admin programs of different types but those are not meant for a 'user interface'. They are are designed so you can develop your own interface thru the web or on the desktop.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
PatHartman - I was posing the question here because people who have not used Access typically recommend staying away from all things Microsoft but there are a lot of people in this Access forum that have experience with various frontend options for mysql.
Dan Craciun and PatHartman - I didn't know that you could use an access front end for a mysql database. That may be the direction I take. If I decide to make the database accessible online it will be far easier with the tables already in mysql.
Peter Harris - I'm intrigued by Filemaker because it seems like it's easy to create an app for my iphone with that, but I'll probably have to try it out for a bit to see if it can do what I want. Looks like I'll have to experiment a bit.
Does anyone have something they would recommend I use for developing a frontend for a mysql database? I found this list, but it didn't give a recommendation and I'm sure there are others that may be better in the five years since this was published. http://www.databasejournal.com/features/mysql/article.php/3880961/Top-10-MySQL-GUI-Tools.htm
Dan Craciun and PatHartman - I didn't know that you could use an access front end for a mysql database. That may be the direction I take. If I decide to make the database accessible online it will be far easier with the tables already in mysql.
Peter Harris - I'm intrigued by Filemaker because it seems like it's easy to create an app for my iphone with that, but I'll probably have to try it out for a bit to see if it can do what I want. Looks like I'll have to experiment a bit.
Does anyone have something they would recommend I use for developing a frontend for a mysql database? I found this list, but it didn't give a recommendation and I'm sure there are others that may be better in the five years since this was published. http://www.databasejournal.com/features/mysql/article.php/3880961/Top-10-MySQL-GUI-Tools.htm
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If I decide to make the database accessible onlineIf that is where you are going with this, Access is a poor choice. Access web apps are wedded to SharePoint and are seriously limited in what they can do starting with no programming language support. If you can't do it with a macro, you can't do it so be sure to carefully review the macro list before embarking on the Access Web app path. Also, there is NO conversion from the standard client/server app to a web app. It will be a complete rewrite, plus the Access web app since it is welded to SharePoint will only support Azure as the database. It will not support MySQL
The propaganda (and we know how believable that is) for FileMaker says that the "same" app can be client/server or web with no changes. I would investigate that very carefully. Also FileMaker Pro requires a proprietary database server which isn't cheap and doesn't offer the free runtime that MS offers for Access. So FM will be a more expensive path.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
decoupling your User Interface from your Data LayerAnd that puts you straight into MVC terrain.
MVC is a very valuable paradigm to learn, albeit a bit difficult to grasp at the beginning.
^ absolutely Dan.
MVC / n-tier design etc - keep your layers separate and you'll build a much more robust solution.
They do take a little longer to get your head around, and certainly need some careful pre-planning before diving into code, but well worth the time and effort in my opinion :)
MVC / n-tier design etc - keep your layers separate and you'll build a much more robust solution.
They do take a little longer to get your head around, and certainly need some careful pre-planning before diving into code, but well worth the time and effort in my opinion :)
ASKER
Gustav - I'll check that out. However, this application will primarily be for use within my company. Very few users. If I make an app for my iphone it will just be for my use to access very few tables.
PatHartman - Thanks. That's what I found out when we tried to take some of the last database online. It was impossible.
Chris and Dan - I'll look into that. I always split the tables from the gui, but I'm leaning now toward making the tables with mysql and starting with an Access frontend. I didn't realize that was possible before. I think that will give me the most flexibility in the long run in case I want to make something for my iphone or accessible for clients in the future online.
PatHartman - Thanks. That's what I found out when we tried to take some of the last database online. It was impossible.
Chris and Dan - I'll look into that. I always split the tables from the gui, but I'm leaning now toward making the tables with mysql and starting with an Access frontend. I didn't realize that was possible before. I think that will give me the most flexibility in the long run in case I want to make something for my iphone or accessible for clients in the future online.