Migrating away from MS Access - Suggestions Please

<<I want to get away from Access.  >>

 What issues are you trying to address?

 Really for a single do it all tool, the features that it offers, and the price, there's not a lot out there.

 There's always File Maker Pro and Alpha 5, but you'll be pretty much right back to where you are with Access when your done.

Jim.

LibreOffice Base is OpenSource and free, similar to access but still different. As database backend on the server you could use MySQL or Postgresql.

A thirty day demo of Filemaker with the 14 templates would give you an idea of it's features.
http://www.filemaker.com/products/demos/
Filemaker is currently offering a 2 for 1 promotion. Offer expires December 18

<<<<My app has grown from 1 to 3 databases over 10 years >>>

I would first evaluate why you have 3 databases as opposed to using just one db with multiple tables to contain all of your data.  You can probably re-design your application using one Access db on the server then link to your 3 user pc's.  I db size is the issue then migrate your data to MySQL or SQL server to the database then design your desktop GUI in Access to link up to your server database tables.  Either way  ... based on your opening post ... Access sounds like the best tool for you going down the road especially if you want to design/maintain it.

ET

If money is an issue, I doubt that Filemaker will work for you.  Plus your client needs to buy it as well as a server.  The O365 subscription is excellent.  For $99 per year, you can get 5 copies of the full office suite that you can install you your computers or those in your household.  This version is not intended for business use so it wouldn't work for your client but it would work for you and is about as low a cost of entry as possible once you get beyond free.  

You seem to be blaming Access for the current disorder in your three applications.  I would look some other place to assign blame.

Start with an analysis of the three applications and decide where their touch points are.  
1. Do they share tables (or if they don't, should they)?
2. Are they all used to fulfill the same business process causing users to jump from one to another?
3. You don't have sufficient users to warrant a move to SQL Server but do you have sufficient data?  I have Jet/ACE databases with millions of rows that operate just fine.  SQL Server Express is free but simply converting Jet to SQL Server is more likely to make the application slower than faster.  The conversion needs to happen based on some understanding of client/server apps and will require at least some minimum query/form changes if you built traditional old-style Access apps.

Just those first two questions should get you thinking about a new structure.  Perhaps the BE's should be combined to make data usage more efficient and prevent dual data entry but the three FE's could remain separate to allow for better security and task separation.

My current database system is fragmented and disorganized.  I put it together piecemeal over the years.

What are the advantages using SQL Server vs SQL Server Express vs MYSQL

Or should I ask that in a separate EE question.  (I get scolded by members if I include too many questions on an EE post, OR, I get scolded if I close a question prematurely and ask a related question in new post.)

So, please let me know if I should close this question first and ask the above question in another post.