I have an Access 2010 DB that is split into FE/BE (with BE in an .mdb format).
I'm a novice at this, but am working on a VOLUNTEER project with 4 other users, each of whom are just volunteers (i.e. no central server, no biz involved). The users live in different cities and travel alot but each has a laptop (all but 2 have MS Access; I'm hoping to deploy via Access Runtime if needed).
We all need to be able to view/edit the DB tables, and sometimes simultaneously. I've already been down the Sharepoint road, and it's just not working, and there is additional cost involved (and getting these folks to move beyond an excel spreadsheet is already a pain). I also have another upcoming volunteer project that begins in a couple of months that is basically the same situation (including getting folks to see the benefits of relational DB vs flat spreadsheets).
I have GoDaddy hosting for my personal website, but that product provides 2 SQL server DBs (or 25 MySQL but I'm even less familiar with MySQL).
SO -
I've installed SQL Server Express, and I've created an SQL Server DB with my Godaddy account (but it's empty). I'm trying to figure out what I have to do in order to get the .mdb BE tables loaded into the SQL Server and linked to my Access 2010 Front End, and then what I need to do to get it working for the other users.
I know this is not a perfect solution, and we all recognize that there may be some speed issues (although my DB is not that large - 5 tables with <200 records apiece, and one larger table with about 1000 records). I'm certainly open to other ideas, but I've not been able to find anything that doesn't require an outlay of $$ beyond what we have.
Only 2 users will need to do any queries/reports (and that could just be me if that's what's necessary).
I'm a novice at this, but am working on a VOLUNTEER project with 4 other users, each of whom are just volunteers (i.e. no central server, no biz involved). The users live in different cities and travel alot but each has a laptop (all but 2 have MS Access; I'm hoping to deploy via Access Runtime if needed).
We all need to be able to view/edit the DB tables, and sometimes simultaneously. I've already been down the Sharepoint road, and it's just not working, and there is additional cost involved (and getting these folks to move beyond an excel spreadsheet is already a pain). I also have another upcoming volunteer project that begins in a couple of months that is basically the same situation (including getting folks to see the benefits of relational DB vs flat spreadsheets).
I have GoDaddy hosting for my personal website, but that product provides 2 SQL server DBs (or 25 MySQL but I'm even less familiar with MySQL).
SO -
I've installed SQL Server Express, and I've created an SQL Server DB with my Godaddy account (but it's empty). I'm trying to figure out what I have to do in order to get the .mdb BE tables loaded into the SQL Server and linked to my Access 2010 Front End, and then what I need to do to get it working for the other users.
I know this is not a perfect solution, and we all recognize that there may be some speed issues (although my DB is not that large - 5 tables with <200 records apiece, and one larger table with about 1000 records). I'm certainly open to other ideas, but I've not been able to find anything that doesn't require an outlay of $$ beyond what we have.
Only 2 users will need to do any queries/reports (and that could just be me if that's what's necessary).
