Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

should i write an access front end or c# front end?

I have an Access database currently. There is a backend, and there are multiple users who use this database with their own front end. The size of the data is very small; however there are several forms that are constantly in use.

I need to migrate the data to MySQL. Should I continue to use an Access front end or program my own c# front end? Why would one be better over the other?

like image 278
Alex Gordon Avatar asked Aug 02 '10 01:08

Alex Gordon


People also ask

Does Access have a front end?

When you split a database, you reorganize it into two files — a back-end database that contains the data tables, and a front-end database that contains all the other database objects such as queries, forms, and reports. Each user interacts with the data by using a local copy of the front-end database.

Can MS Access be used as a front end for SQL Server?

A common use of Microsoft Access is to keep it as a front end to more commercially successful DBMSs. For example, Access can attach to an Oracle database, so business applications written in Access can connect through to data held in an Oracle database. Access can also front for SQL Server and Sybase.

What is the advantage of using Microsoft Access as a frontend for a MySQL server database?

There isn't a better desktop database solution for building user-friendly frontend applications than MS Access. By linking MS Access to MySQL tables, it is possible to have robust data storage capacities married with robust user interface capabilities. In addition, this model allows for additional hybrid capacities.


1 Answers

I think you all are either completely crazy or don't know a damned thing about Access.

It is certainly true that the upsizing tools for SQL Server are easier to use than anything available to you for upsizing to MySQL. But the difficulty of upsizing should not drive your choice of back end, because it's a one-time choice. Choose your back end database based on what works best for you. While SQL Server Express is free, it has a number of limitations that MySQL itself does not have.

As I said in comments, you can export an Access table to MySQL by defining a DSN for your MySQL database and simply using the EXPORT command on the Access file menu. The results will not necessarily be perfect, so you might have to tweak the results, truncate the MySQL table and then insert the real data once the MySQL tables are all in place. Yes, this is more work than the SQL Server upsizing tools, but it's still pretty easy to do.

And it's not something you have to get right on the first go, nor do you have to do it multiple times.

If MySQL is your preferred database engine for your app, then go with it. Using SQL Server entirely because of the more elaborate upsizing tools is really a case of the tail wagging the dog!

like image 65
David-W-Fenton Avatar answered Oct 12 '22 22:10

David-W-Fenton