I've got a bit of a conundrum.
I'm doing a consulting gig where we started out documenting workflow processes
via capturing screenshots and putting them in powerpoint along with a description.
It was easy and the girls were familiar with it. (I wrote an autohotkey script). Powerpoint also makes it nice to view full screen.
The problem is that the processes grew to over 100 and now it has become unruly to maintain. (sometimes we need to add meta data to each process for analysis purposes)
I'm thinking a database. Access? MYSQL? I've never used either.
Requirements:

• girls on different machines in different departments should be able to input screenshots and a text explanation
• some sort of form to guide their input (they enter all kinds of irrelevant data otherwise)
• to be able to display the content in a powerpoint or similar presentation(we actually uses OpenOffice since many machines didn't have powerpoint)

A few years ago I did quite of bit of coding SQL for a MS SQL DB. (but I may have forgotten a lot of it)
Any help appreciated!

Maybe something like MS Project might be a better choice.

I'm not seeing how MS Project can work but I'm not very familiar with it's features.
I'm mapping workflow processes so that we can analyze them for inefficiencies and waste.
In some of the departments most of the employees processes are done on the computer
and hence the reason for documenting the steps with screenshots.
Some of the metadata that we are attaching to the processes are things like:
total # of steps, start/stop time, earliest start and latest start times, suppliers, customers, input,
output, etc.
The powerpoints were a great solution early on because we didn't know what we were getting
into. Now they are unruly.

How do I edit posts? I've been looking for 15 minutes. Is there any way to edit posts on this forum?

test

There is an edit button at the bottom right hand corner of your posts.

I use access because I know how to.
I use access to store processes and procedures, where a procedure is a set of processes. Can also store pictures for each process. The key is not to store the picture itself in the database (you can do this if you want to use heaps of memory) but to store the location of the file in a text field in a table. You can use an Image control to display the picture in a form or report easily

hope this gets you started

This post has been edited by multicoat: Mar 30 2012, 05:18 AM