I am someone with a very small amount of database experience. Like, I can set up a database with a few related tables, make forms, reports, queries, all the basic things. And I've only worked with Access.
We currently have a database set up in SharePoint meant to track various organizations, what populations they serve, what offices they work with, contact info, that sort of thing. I also, independently (because nobody knew we needed what I was working on to interface with the Share Point stuff) made my own version in Access. Mine is a pretty basic setup, with two tables (one for orgs and one for advocate offices) connected by a many to many relationship.
Except now we need my stuff to connect with the SharePoint stuff, and also someone mentioned MySQL (actually they mentioned something that was a bunch of letters and started with an M and was pronounced like a word but wasn't really a word), so now they want more information.
So.
Before I start dropping a bunch of time on research, I figured I would get any general thoughts in here. Does either Access or MySQL play well with SharePoint? We'd need to pull stuff off of SharePoint, add a bunch of stuff to it via (Access/MySQL), then stuff it back into SharePoint. Does this even make sense as a viable strategy? (They're committed to SharePoint because it's stuff that will be semi-publicly available, and they like it.)
I submitted an entry to Lego Ideas, and if 10,000 people support me, it'll be turned into an actual Lego set!If you'd like to see and support my submission,
follow this link.
Posts
You can also just connect to the database using sharepoint if you add it as an external data source to a list, and then edit it from that, so you don't need to manually pull/push to it if that's what you were thinking.
Good luck!
Blizzard: Pailryder#1101
GoG: https://www.gog.com/u/pailryder