On Wednesday 13 July 2005 12:50, Robert Shaver wrote: > Hi Weiers, > > ADVICE > As you have discovered, creating a complex spreadsheet application can > be complex and error prone. Most people don't realize that they are > developing software when they are using formulas in a spreadsheet, but > they are. One of the most important decisions in any software > development project is choosing the right tools for the job. The wrong > tools can make a good outcome unlikely. > > The first step in developing a new project is requirements. If your > project is easy then the requirements will be easy to write down. So > write them down. You might be surprised at how much this will help you > clarify what you are trying to do. Once you have written down the > requirements, ask yourself this question about each one; "If the system > didn't have this feature would the project still be worth doing?" If the > answer is yes then leave that feature for later. Implement only the > absolute bare essential features first and get something that works sooner. > > MY OPINION > Unless you can reduce the problem to a single sheet, I don't think it's > the right tool for the job. I have done a few multi-sheet spreadsheets > that interact and they were hard to get working and harder to keep working. > > Now some specific questions about what you are doing > QUESTIONS > 1. Why do you need three sheets? Why not just add columns to the first > sheet? If you limit yourself to one sheet then you won't have to worry > about having to update the same values in multiple sheets. (This is > where some development experience can help. You're running into issues > that have been around for a long time and have been solved in many > different ways. Each solution has advantages and disadvantages.) > 2. Have you considered a simple manual system? It's quite amazing what > you can do with a graphite text editor; paper, pencil and eraser. > Computers don't always make things easier. > > I have created literally dozens of systems just like this using Lotus > Notes. Mostly this is because I have used Notes on a daily basis for the > last eight years, developed large and complex systems with it and I know > that it is ideal for small projects like this as well. The closes open > source systems to Notes is Zope or Plone (which is built on Plone). I > haven't used either one so I can't swear to it, but what I've read makes > them look like good candidates. The setup and learning curve would be > steep, however. > > I hope this is helpful. Most of it is just my opinion after about 25 > years of software development. YMMV
I am not sure I agree with your concept of not using oo for a complex multi-page spreadsheet. I have been using a 24 page spreadsheet for payroll of up to 20 employees since 1993. It started in Quattro Pro/DOS and went to OO 1.x about 1-2 years ago, and is now migrating to oo 1.9.x. I have found that the use of multiple pages allows the sheets to remain simple, unlike to "spaghetti code" of basic programs of the 70s and 80s. What you hinted on though was the 'right tool' issue. Often I have seen spreadsheets used for database management. This can be a disaster waiting to happen. -- John R. Sowden AMERICAN SENTRY SYSTEMS, INC. Residential & Commercial Alarm Service UL Listed Central Station Serving the San Francisco Bay Area Since 1967 [EMAIL PROTECTED] www.americansentry.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
