Which database / programming environment to chose

Here my situation: good knowledge of programming in general, good
knowledge on relational databases in general.. no specific knowledge

I've worked in access, SQLServer, MySQL and php (a lot with this one),
SqLite and Ruby/Python...

I need to chose a practical way to develop a program for my company to
manage document lists and revisions.
I need something simple and good reporting capabilities..
What else apart from access and filemaker? Is reporting easy enough in
visualStudio + c# ??

suggestions welcome!
Luca

On 21.08.2008 17:07, Snaggy wrote:
> Here my situation: good knowledge of programming in general, good
> knowledge on relational databases in general.. no specific knowledge
>
> I've worked in access, SQLServer, MySQL and php (a lot with this one),
> SqLite and Ruby/Python...
>
> I need to chose a practical way to develop a program for my company to
> manage document lists and revisions.
> I need something simple and good reporting capabilities..
> What else apart from access and filemaker? Is reporting easy enough in
> visualStudio + c# ??
>
> suggestions welcome!

Difficult with these rudimentary specifications. How many users are
there? Do you need to implement workflows? How large do you expect the
data set to grow? Do you need a web frontend? ...

From what you write I am pretty sure that you can buy something like
that already. Then there would be the question: why roll your own?

Kind regards

robert

no, it's not so big. Would be max 10 users with something like 100
documents, each with a few revisions..
no web interface needed

what would you do?

On 21.08.2008 18:40, Snaggy wrote:
> no, it's not so big. Would be max 10 users with something like 100
> documents, each with a few revisions..
> no web interface needed
>
> what would you do?

I'd probably use something like SqLite and a script language that
supports it. How tamper proof does your solution have to be? In that
case you need something with user management.

Depending on your reports generating them in HTML is pretty easy. If
you need charts then it's more effort.

I'd say take what you're comfortable with.

Cheers

robert