The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
Please vote in the Forum Structure Poll. Polling will close at 2PM EST on January 21, 2025.
The place I volunteer at is kind-of-sort-of growing out of the Access database system I made for them a few years ago. It still functions fine, but over the years things have come up that they wanted to add and feature creep has gotten to the point where it's time for an overhaul. Since they're mostly computer illiterate and never back anything up I've decided it would be a better idea if I just set up a Linux box in the corner with MySQL and cron backups. This also centralizes the data which solves another headache.
Testing things out I've got Access (2007) to read from a remote MySQL database via ODBC. So that's good. My question arises in that I need to do a lot of work to automate everything for these folks so a lot of VBA work ends up getting done. Since the last version was entirely Access I used DAO, however I read that I should be using ADO if I'm branching out.
But DAO actually worked as I tooled around a bit last night. So does it matter? Also if it's going to be ADO is it ADO or ADO.NET?
Beyond that in the last version I made some reports for them to use as thank you letters. This is fine but when they wanted to change the letter they had to go into design view which is kind of overwhelming for them. Do you think it would be easier if I just had them mail merge queries in Word?