>> Text files cannot be locked, should data not be stored in then? PIM >> applications cannot be lock, should data not be stored in them? >> >> > It would depend on the application and usage. We store data in text files > because they are thousands of lines long and we can insure they will be > accessible 5 years down the road where we cannot in a binary file format. >
Which is not different from what Latet is doing with their Calc spreadsheets. >> have you never head of the "DROP * FROM table" without a WHERE clause >> stories? That seems just a bit more dangerous to me. Furthermore, how >> does an end user backup a database? Which files, exactly, does he >> copy? > > No I have not. But I have seen someone wipe out a spreadsheet with a simple > keystroke. Any tool has ways of destroying the data but if it is setup > properly the ability to corrupt data is much harder. > There are enough horror stories about the no-WHERE-clause DELETE statements. What single keystroke could wipe out a spreadsheet? >>> Also, linking between data fields is much easier in a database. >>> >> >> Linking between data fields is not necessary for this application. > > I don't know. I have not seen the spreadsheet. If it is just records to be > calculated then no problem. I read that there were employee numbers being > used and to me, this points to linking data between data identifying an > employee with extra data. I am thinking in terms of how I would do it. > Actually, they are volunteers not employees, but the idea is the same. There is no link to other data, though, just one row per volunteer with some information. One of the columns is an enum, something that is not native in Base. > Again if you feel that spreadsheets are a good place for database data, then > this is a valid comment. If the data is simple like an address book, then a > spreadsheet meets the requirements. > Yes, this is like an addressbook. > Here is a simple document that I feel covers this quite well. > > Using a spreadsheet as a database - what works, what doesn't' work. > http://www.plumsuite.com/Articles/Using%20a%20spreadsheet%20as%20a%20database.pdf > Nice, but nothing new there for me. If it were in Hebrew I would pass it on, but really it says nothing (other than the story) that I have not already told them. Yes, a database would be _better_, but a spreadsheet is _easier_ for them. > Consider moving your database into Access or creating it there if your needs > include: > • Screen forms arranged in a particular way, or that do not show all fields Negative > • Keeping your data consistent in particular fields Positive > • A “bulletproof’ application for routine entry by unskilled workers Positive. however, which unskilled worker is going to make the tables, forms, and reports? > • Linked tables to avoid data redundancy Negative > • More than one person using the data at the same time Positive, but they will be on the same terminal so it doesn't matter. > • Keeping old data for future reference Positive > But this debate doesn't solve the issue of what went wrong with the data in > the first place by the OP but is useful to those that want to know why and > when to use a database over a spreadsheet should be considered. > I do, however, feel that the rounding issue would not have occured in Base. That I will contend. > If the spreadsheet is written properly, it shouldn't be that hard to export > it to Base from Calc. I have not tried it yet. > It was written properly, that much I can say. -- Dotan Cohen http://what-is-what.com http://gibberish.co.il --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
