Scott, I have done something similar with a MS Access database for this purpose. It resides on the university network where anyone who has the "rights" can view it, but only one secretary and I can add to or change it. It sounds like you may have some nice features that I don't, and maybe vice versa. Mine has three Tables: Pianos, Service Dates & Info, and Technicians. With this set up, you can define a time period and see (among other things): 1) All the work done by any one technician 2) All the work done to any one piano 3) All the work done to all pianos by anyone For Jim, text fields are limited to 256 characters, but memo fields are pretty much unlimited. I would like to see what you have done, and would be glad to share my set up with anyone. John Baird Millikin University Decatur, Illinois "Scott E. Thile" wrote: > Hi Jim and group, > > I use Microsoft Access on a PC to accomplish this, and I know that Don > and several others use FileMaker Pro on the MAC in a similar way. I > used it when I was a slave to the MAC platform here as well. :) > > The approach that works well for me is a "One to Many" type relational > database. > > The "One" is a database with the static type records of each piano, > info and assignment, and over all conditions. The serial number serves > as the link between this database and the "Many"database. > > The "Many" database is based on a form for each service performed. > Again, it is linked to the "One" database with the serial number of > the piano. The basis for this database is a service record form that I > use for each service. I type in the pianos serial number. The rest of > the information fills in from the piano database automatically as well > as some default service information. All I have to do is enter the > notes for that service, and the temp and humidity readings and > previous pitch etc... Then save it. Takes me about a minute at the > most to do this while at the piano. (I have my laptop out with RCT > anyway, so it all works great together). > > I have my database designed so that when I pull up a piano record in > the piano database, all the service records (from the Service or > "Many" database) that relate to that piano appear in a scrollable > window, along with any notes from that service. > > I can generate reports to track my time, tuning fluctuations due to > humidity, work needed information, etc from one or both of these > related databases. > > Scott > ---------------- > At 11:35 AM 2/5/01 -0500, you wrote: > >> > Computer data base should be kept on piano inventory, condition, >> history, >> > repairs, scheduling for future work, etc. >> >> Still on subject, I think. I recall variations of the >> record-keeping >> theme have been mentioned (only) here before. However, I've yet to >> see a preferred method to accomplish this. >> >> It's relatively easy to log names, serials, physical locations, >> etc., >> on just about any platform -- database, spreadsheet, or even a >> word processor. These items, with the possible exception of >> location, often remain static throughout the service life of a given >> >> instrument. However, the service history tracking and verbal >> recommendations would be in constant flux. >> >> In short, I'm looking for suggestions on how to best accomplish an >> on-going log, complete with service history and free-style notes. >> This could in the form of a spreadsheet matrix or database field >> headers, or any other method this group has found to be effective. >> >> In my position as a subcontractor, I'm trying to present a >> chronological accounting for "I told you so" purposes to >> administration. In the past, I've predicted (and documented) that >> [certain unit] is likely to fall below minimal service requirements >> within [length of time]. When my suggestions go unheeded, and >> someone says "Why didn't you tell us?", I want to have everything >> about a particular piano all in one place. >> >> Thanks for any ideas/considerations in this area. >> >> Jim Harvey, RPT >> >> >> Jim Harvey >> harvey@greenwood.net >> Greenwood (n): the largest city in South Carolina WITHOUT an >> Interstate > > Scott E. Thile, RPT > Piano - Instrument Technician > ---------------------------------------- > Murray State University, Murray, KY > mailto:scott.thile@murraystate.edu > (Work Website) > http://campus.murraystate.edu/staff/scott.thile/index.html > (Ham Radio Website ) > http://campus.murraystate.edu/staff/scott.thile/k4set/index.html > (Family Website) > http://campus.murraystate.edu/staff/scott.thile/family/index.htm > (Nickel Creek Website) http://www.nickelcreek.com/
This PTG archive page provided courtesy of Moy Piano Service, LLC