Question Alternatives to Access Back-End?

[M_S_Jones]

Hi,

I've got an Access database system in place at the moment which has a lot of users, and which has a lot of automated procedures updating temporary tables with data from our SOP. It works well enough, but on occasion, probably about every 3-4 weeks, the back-end appears to corrupt. I get a message saying that the format isn't recognised. Opening the back-end and letting Access repair it nearly always fixes the problem.

I've got quite a few Access systems that are currently live, and I don't get this with any of the others. I suspect this problem is caused by volume of use. My question is whether I would be better to host the data in another technology that was better suited to handling this much activity? Ideally, if I were to change, I would like to keep the front-end as it is, and just join to another data source. If it would be best to change, which technology would I be best to change to? I've seen on this forum people using SQL Server, MySQL, PostgreSQL etc, which technologies come highly recommended for use with an Access front-end?

Thanks,

Matthew

 

[Galaxiom]

Move the temporary tables out to a separate database and see if that fixes it.

If you want to upgrade the back end I would suggest MS SQL Server Express. The 2008 R2 version will support up to 10GB of data and its is free.

 

[RainLover]

Where are the Temporary Tables.

On the Front End or Back End.

I would use MySQL.

Most web sites would be created using MySQL.