First, please be aware I am definitely a beginner when it comes to server maintenance or network administration. That being said, if I am asking this question in the wrong forum, please feel free to redirect me.
Despite my lack of experience in the IT field (I'm a mechanical engineer), I am still by far the most qualified in our small office to handle issues like this. I was a software consultant for several years out of college, so I can recall enough SQL and C#/C++ to get by if I need to, but want to keep it as technically light as possible.
Right now I'm using Excel to handle all documentation control and product data sheet creation. These are functions probably best suited for a database. I've toyed with OpenOffice Base as a good free alternative, but unless I'm missing something, it seems to come up short on features that a full-fledged SQL Server or PL/SQL database would have.
This should be expected, seeing as it's free, but I hear a lot of talk about mySQL as a good starting place, especially if I intend to start publishing reports or creating forms for data entry.
On all of these issues I'm a bit clueless, but first thing's first: What is the best option to get started with a database product (preferably free) that I can develop into an office-wide server once I know what I'm doing?
Best Answer
It's a small office. That sounds like datasheet import / report generation. I'd say don't bother with concurrency problems, high availability and such, but with how to integrate existent base. I don't think you need all the available SQL power more than you need good integration/migration tools.
My 2 cents is: go and see if the features of OpenBase meet your current requirements. If so, go with it. If you really know you need the SQL power of mysql or postgresql you can start using OpenBase as a frontend with either one as a backend. As far as I can tell, mysql/postgresql aren't exactly seen/used as office solutions so in your case you may not get all the help you need when asking for it on the community forums. I advise against using these directly for implementing office solutions. On the other hand I vouch for OpenBase to be used at least as a frontend, if not together with its "native" sql backend, hsqldb. You will be able to easily integrate current solutions and/or migrate existent data. OpenBaseis a good alternative to microsoft office solutions so I won't bother talking about the latter here.