Okay I'm looking to set up a web based service that for the most part is only used to display data to a number of users. Now initially I'd decided to make something using Sharepoint (2003) as the front end and MS Access. Now I realise that these wouldn't be anyone's first choices but here are the reasons why:
- Using Sharepoint makes it easy to tack on to the existing intranet.
- Sharepoint has good Access integration.
- Concurrency in Access isn't an issue as it's largely going to be read only, and only one user is ever going to be writing to it at a time.
And finally because getting IT to support anything else is a real chore. Now initially I didn't think I'd have much of an issue setting it up due to the aforementioned Access integration. However now I've looked into it I've discovered that it seems to be a one way street. You can link Access to Sharepoint Lists, but you can't link Sharepoint to an Access database. This is a problem as ideally I don't want to store the data in Sharepoint. We'll be migrating from SP2003 to 2010 sometime in the future and I want to ensure the database is preserved. Wouldn't be an issue if it was going to be purely read only, as I could keep all the data in the database and just periodically push it to the lists in Sharepoint.
However one application of the system requires the ability to write to the database. And as far as my google skills have revealed there isn't an easy way for Sharepoint to push back to the Database.
Is there a way to do what I want with the tools I have? Or would I just be better off scrapping it all and building myself something with ASP? I have done this kind of thing before but web development has never been my speciality and I'm very rusty and on a deadline. What's the path of least resistance here?