MS Access and My SQL

[Oneclo1]

I have a access database with forms, quires, and reports. i have multiple buttons to run or access them. i want to run it so other employees can access it via the internet, but without the access menus. im guessing Mysql, can anyone tell me how to get the Access DB to run in MySQL, or does anyone have an idea how to accomplish this?



Thanks

[NoellaG]

The important question is: do the users have to manage / update the data or only the reports? In the first case you will need something like PHP or .net on a MySQL, SQL server (express is for free) or Postgresql . In the second case (only report reading) I would suggest SQL server with reporting services/report builder (this can be installed for free together with sql server or SQL express).

[CJ_London]

mySQL is just a database, it does not include forms/reports etc. So you cannot 'get an access db to run in mySQL', only the backend.

another alternative is to use sql Azure for the back end - and as with the other suggestions, with the Access front end on the users local machine.

In all cases it is possible the SQL will have some differences from Access SQL so you may need to modify your queries - and ideally place them in the back end

You can use code to hide the access menus. Plenty of examples of how to do this on this and other Access forums. A simple hack (which is easily overcome by knowledgeable users) is to rename your .accdb/e as .accdr, however if your app relies on users being able to use the shortcut menus for sorting/filtering etc, you will need to write your own since these are disabled along with the navigation window and most of the ribbon.

If you mean the front end is also on the internet then look at using terminal server or citrix - this is the easiest way to migrate an access app to the internet as other than relinking to the back end there should not be anything else to do.

Anything to do with the internet comes with a cost - potentially licensing costs and hosting costs.

Note that your front end needs to to make efficient use of data transfers otherwise it will be very slow (exception being TS or Citrix) - so no forms based on tables, base them on queries with criteria to limit the number of records to bring across. No use of VBA functions, build the equivalent in SQL. If you have to apply a VBA function to the data, do it after you have downloaded the data.