They (DB's) can be tricky things to master thats for sure, but if done well, can also work very well. I'm sure (although I'm definitely no expert) that there would be a way of producing a start / finish stopwatch type of event on a form. The difference between the two could then be saved to the DB.
Have fun... /paul On 7/30/06, Eric S. Johansson <[EMAIL PROTECTED]> wrote:
Paul wrote: > Sounds like a form that saves the entered contents to a database is > what your after. Properly constructed you'll then be able to build a > variety of reports that extract the information based on what has been > entered for various clients/customer types. > > Database can be either the internal format, or connected to an > external product (eg, mySQL, etc...). Have a look here for guides on > working with base : http://documentation.openoffice.org/ thanks. The timer is going to be a hard thing. I need to be of the start stopped and switch between different forms. I think (but I'm not positive) that I need to display different sheets for different customers. in many ways I think of this as like a gigantic sticky note that has a few predefined fields. And likes taking notes, I can have multiple instances visible at the same time. I will take a look at base. I must admit I've avoided databases for applications development for well over 30 years as every development project that was on that use them typically went 200% to 500% over budget instead of the normal 75% to 125% ;-) ---eric
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
