[Graham:] So certain things on testing. You're probably very proud of your masterpiece, and erm, there's ot there's the temptation to keep making minor improvements, just to make it a bit better. Er, but any change you make to a computer system, is likely to introduce bugs into the system, so that it doesn't give the right answers any more. Er, so you have to resist that temptation. If there's something that isn't working, there's a well known adage with computers, don't fix it. Erm, what you need to do is, if you can, save up all the changes, for one batch and then do them all together. Cos there's economy to scale on, first economy is the scale on understanding the system. Before you can make changes to the system, you have to understand it, and that takes an awful long time. Er, so there's economy to scale on that, and there's the economy to scale on testing too. If you have to test... an something, then there's economy to scale if you test the ten things instead of one.... Erm, when you start testing, you shouldn't input the real numbers, to start with. You shouldn't start with nice simple constant numbers, maybe thousands all the way across, cos the eye's very good at detecting irregular patterns, and when you put nice simple numbers in, the eye can see these irregular patterns clearly, and highlighting errors. On this spreadsheet here, I haven't input my s constant round numbers. [cough] If you look at that spreadsheet, then nothing seems wrong with that, seems okay. seems wrong certainly. But if I put nice round numbers in, the green cells are the input cells. Thousand across all the columns here, erm, nice round numbers input elsewhere. Then most of the, the rows also come out with nice round numbers, except this one row here, stands out. Numbers look a bit odd there. I'll have to investigate. So you start with nice, you may then change one or two of the numbers, to check various aspects. You start with nice constant round simple numbers. There's all sorts of ex it's probably impractical to test every single cell. You have to concentrate too on extremes, the first and the last in a row or a column. Erm, there's no many different aspects of two extremes. Does anybody here write spreadsheets for other people to use? So it's solely for your own use. If you write a spreadsheet for somebody else, you might be using a sixty six megahertz four eight six duel processor erm, spaceship, and, somebody is using a steam driven I B M A T or something, and it runs quite acceptably on your machine, a reasonable speed, and you give it to somebody else on that steam driven thing, and it takes ages to do anything, and er, you press a button and they wait half an hour... sort of thing. This happened to you... some way or other? You need to research into this, don't you? But it's given you a spreadsheet it takes ages to load it
[speaker002:] even load it.
[Graham:] So, there's that to consider as well if you're writing spreadsheets for other people. Erm. When you finish testing, well, as you test you start off with simple numbers and you then start changing some of the numbers, to test other aspects, and eventually you're happy that everything seems to be working alright. Now, what you probably do is just reset all the input cells back to zero. Erm, and you lose that test data set. It's a good idea to keep that test data, because later on, you're almost certainly going to make changes and you'll therefore need to re-test the system, and a quick way to re-test the system is to put all that test data in again and see if you get the same answers. And if you don't, then you can see very quickly what's gone wrong, and probably where it's gone wrong, as well. So, keep that test data set. That's another good reason for keeping all your inputs in a separate area. It then makes it easy to save all your inputs into a separate file, when they're all in one separate input area. If you've got them scattered about all over the place, it makes it much more difficult to try and save them, and, later on, get the data back in. It's very easy to do all in one separate area combine and put the test data file back in again, but very difficult when scattered about. Erm, said that. No matter how erm, simple or small a change you're making, you'll probably think oh, that's bound to work, no need to test that, such a simple change. You'd be surprised. You have to test every single thing. Now even if you test things thoroughly as you're building your spreadsheets, then it's quite possible that something you do later on affects something you do earlier on. So, you need to go back when you finish the whole system, and test everything again. Erm, but you won't remember all the things to test, as you forget very quickly, so as you're building the spreadsheet, you ought to write down a list of things you're going to go back and test. Sorry. that's a point testing certain aspects. It'll often pay to think about er, the order in which you test. Because if yo if you got to the end of testing and then you found an error, you might have to go all the way back to the beginning again, because what it affects affects something that you did earlier on, so you have to go back and test everything again. But if you thought about the order that you test, then, if something doesn't work, you may only have to go back a few steps and re-test. When do you enter? Yeah, well, that's a fact of life for the boasts out. I suppose you might a very simple spreadsheet, then er, just adding up a column of numbers is hardly get that wrong. Er, that's true. But then there are underlying boasts in One Two Three and in DOS and a certain rare combination of circumstances, it's possible that. It's highly unlikely that summing up a single column of numbers. But it's possible. This could be certain circumstances, and there are, when you get the wrong answer. That column of numbers. If you knew what the combination of circumstances were, then you could perhaps re-do your spreadsheet with a different way to avoid it. But, er, you're not going to know all bugs that there are in the software. But having said that, if the something doesn't work. Well, human nature being what it is, then erm, you're likely to blame Lotus. So oh, Lotus is not working properly. But ninety nine times out of a hundred, it's your spreadsheet that's at fault. You had this experience before? Blamed it on Lotus. Test, er, documenting in the next topic. The same reasons as er, testing, er, you ought to do it as you go. Because if you come back later on, and try and document your spreadsheets, then an awful lot is forgotten. So you have to spend time or time to re-understand what you were doing before you can document it properly. When I write a system for a client, then I do the documentation in advance... of writing the system. Erm,an another advantage of doing that is, it ensures that you do in other things, which is design a system. Nobody documents the spreadsheets. Nobody designs the system. People just jump straight in, do the first bit, erm, having done the first bit, they then think about how they're gonna fit in the next bit, and you end up with a rambling mess that er, doesn't fit together, doesn't work together too well. If you plan things as in most in life, if you plan ahead, you can actually er, do it a lot quicker. And that certainly applies to building computer systems. Planning ahead, building your spreadsheets. You probably end up writing the system file quicker, and have a much simpler system which also maintain in far less time. You can also have far less errors etcetera. So, if you do the documentation in advance in the documentation... yeah, in the documentation, I explain what spreadsheets there are, where things are on the spreadsheets, the various procedures for how to do certain things. You do this, this, this, go here and there, and go there, do that and so on. You've actually thought through exactly erm, how the spreadsheet is going to be designed. Er, now certain documentation are very valuable. One of those is the spreadsheet map. It's a bird's eye view as to where everything is on the spreadsheet. So this is the whole spreadsheet, and erm, these green boxes within the spreadsheet, are the different areas within the spreadsheet. Erm, so in the top left of this spreadsheet I've got some documentation, below that some blank rows, a key parameter section here. Below that to the right, is some imported data, and so on. So I know where things are on the spreadsheets. And not only that, I've written some text on the spreadsheet showing the process that's going on. So the first thing that happens is data gets er, imported into the spreadsheet here, and second thing that could happen is er, the unwanted records get deleted. Step three, is something called run flags, so something specific to this spreadsheet gets extracted, and so on. So I've got a good idea what's going on on that spreadsheet, what's on it, where it is, and what's happen what happens in the processes. They're very useful pieces of documentation. As I was saying before, the most important thing to understand is the overview. Once you understand the overview, you can start to work your way, and understand the individual detail. Er, it's a good idea to got documentation actually on the spreadsheet itself, because then it doesn't go missing. [cough] I'll put the file name, the date, and time, that's what we were talking about before. If you want a file naming convention, you might want to explain the different elements of the file name. Erm, if you're responsible, you might want to put your name down, if you're the creator of this spreadsheet. You probably don't want to do this, I would imagine. But anybody who inherits your spreadsheet in the future erm [phone rings]... Anybody who inherits your spreadsheet in the future may want to understand something about it, so you're obviously going to be a good source of providing that information. Or there's anybody in your own organization who is responsible name the PCs and the files etcetera may want to know, is this your file. Do you want to delete it or whatever. It might be useful to know who was doing that. Erm, even if you inherit some spreadsheets from this person that's left, that's useful knowledge because you don't have to spend time searching for whoever might have created this spreadsheet.
[speaker002:] Erm, this is a general method spreadsheet that Harlow's code handled it applications and department say that erm,
[Graham:] Did you hear that?
[speaker002:] Yeah.
[Graham:] She had to stay here to midnight. [LAUGHTER] [cough] Right, erm. So, er, what the description was there by the way, it's not meant to be a description of the person. What it is, is this thing that follows, is that any changes you make, any modifications are likely sources of problems. If... somebody calls you up and says something's not working, always ask, well what did you change recently, and ninety five percent of the time, it's that that's the cause of the problems. The that they changed recently. So you want to make a note of what's changed, so when you make a change, who made it,. A description of the change. Why does this spreadsheet exist? So that's an important thing to know. What's the overall purpose of this spreadsheet? So here is some text explaining that. On this slide I've kept the text pretty small, because stays on this line, but er, you've got more text than I've got there, to explain the purpose of this spreadsheet. and very importantly is er, a list of instructions on how to use it, in order to erm, update it for the current month. You do this, this, this, this, this, this, this, this, this, this and this. To do some other tasks, you do this, this, this, this and this and so on. So you have a list of procedures for erm, what you have to do, and this one will certainly be very useful to anyone else, who's going to use the spreadsheet. But it's also useful for yourself, because you can forget a couple of steps, even though you've built this spreadsheet, and er, when you update this spreadsheet for the following months, you know, occasionally you might forget a step. Well, it's like you check the lists, you can quickly, even if you think you remembered it, [cough] you can still quickly read through to see whether you've done all those different things, and you do sometimes forget, so it's useful for that as well. Er, if you were writing a written article, then you may well include references, or sources of information that, that help you write that article. Same way on your broad spreadsheets, you may include sources of references, mainly people that you've spoken to, that provided you information. Maybe various manuals, such as the Lotus manual. You may be using some particular part in the spreadsheet that you consider to be unusual, er you may want to include a page reference, so that er, [phone rings] you can understand it again...
[speaker002:] [phonecall starts] Hello, yeah, yeah, I'll get him to call you back, then, bye, bye [telephone conversation ends].
[Graham:] Er, then... then it, when you're looking at the back, unusual part of the Lotus again, you know which page of the manual to go, or all of the help screens. Tells somebody how to get to particular help screens or people often have difficulty finding things on the help screens, so, some instructions for where to find a particular piece of information on the help screens can be useful. You can create a basic form of map on the spreadsheet. In fact the whizzy-wig, whenever you use it, you don't have to actually draw a diagram, that map that we just saw with boxes and arrows and things, you could draw that on the spreadsheet with the whizzy-wig. On a text spreadsheet though, you can't draw things, but er, you could use some letters positioned roughly where the different parts of the spreadsheet are. So you could, you could create a crude form of map on the spreadsheet, particularly on a text spreadsheet like this. Good idea to have a list of all the file names, cos er, you may want to copy this system to some other computer. But you you'll probably, I would imagine, over a period of time, put a number of extra files in that directory that you're going to need. So identify which of the files you need, er, would be useful, so that's what this would do.
[speaker002:] Sorting them
[Graham:] Okay. Thanks very much, and if you er were to er, accidentally lose some files, you would know which files have gone missing. Er, another useful piece of documentation, is a diagram listing all the files that you've got in your system. So there's a box for each file, and there's a flow of data from one file to another, a little arrow showing how the data passes from one file to another. Er, it'd be a good idea to also write the file names. These are just the descriptions, but the file names would be useful to appear on those ends of those boxes as well. And if you were to write a manual, er, though that's probably unlikely for most of you. Basically, if you write a manual for somebody else to use, then er... there's a standard layout of manuals, computer manuals, that is to have a Getting Started section, tells you how to instal in... some of the basics like how to start it running, erm, the How To section is very important. The procedures and how to do certain, certain tasks. You ever used a Lotus manual?
[speaker002:] No.
[Graham:] A lot of people don't. Never seen it most people, I don't think. Er, but they have a lot of steps on how to do things. You do this, this, this and this. For all sorts of different tasks. So that's probably the most important part of the manual. Er, with reference section, perhaps describes all parts of the system, and the index is very useful, even though it's only a dozen pages long, your manual. So if you're looking for something, [cough] bit of a pain having to wade through half a dozen pages, if you can go to the index and then jump directly to the relevant page, and then save you a bit of time. On most modern word processing software, it makes it very easy to create an index. Ho who uses any word processing software. What software do you use?
[speaker002:] Couple Playwrite.
[Graham:] Playwrite. I'm not sure I'd call that modern word processing. Does that cre create indexes for you?
[speaker002:] No.
[Graham:] Not that you're aware. Oh, right. Okay. It it's that what you're used to...
[speaker002:] No Word for Windows
[Graham:] Word, Word for Windows, which certainly is, that is a modern word processing package, right. Er, er, any questions on that. Er, have a quick revision, then our final test... Oh, right, okey-doke, alright, thanks very much. Bye-bye.
[speaker002:] See you, Bobbie Bye. Bye, Bobbie. Cheerio. Have a nice weekend. Thank you very much.... [revision]
[Graham:] Did you want to go on this side? So the last time we had a break was er, well, actually, we didn't do the useful formulae, did we, last time? So we can include that in it.... Right, are you ready?... Right, I think it's the left turn to go first. Erm, if you got er, a label in B three and another label in B four. How do you enter a formula that joins them together?
[speaker002:] Plus B three ampersand B four.
[Graham:] Right, good.
[speaker002:] Right. [LAUGHTER]
[Graham:] Er, if you got a, a number in one of the cells that you're joining. You got a label in one cell and a number in another cell, you want to formally join the two together, er, what's the formula?...
[speaker002:] ... B three B four.
[Graham:] B three B four?
[speaker002:] Yeah.
[Graham:] So the number is B four, let's say. Yes, it is. That's right... plus...
[speaker002:] do you think B three...
[Graham:] B three, B four's got the number.
[speaker002:] plus B three, erm... and you got a brackets, that way and erm, B four has the at stream...
[Graham:] At stream, yeah.
[speaker002:] Open brackets... no, at stream, open brackets...
[Graham:] Yeah.
[speaker002:] B four
[Graham:] Yeah.
[speaker002:] Close brackets.
[Graham:] Oh, yeah, er, give you half for that. Put it across to this side, you know the question
[speaker002:] Never done it before.
[Graham:] You didn't get it quite right...
[speaker002:] The brain
[Graham:] [LAUGHTER] There would be a plus in front of the... ampersand... comma zero you missed th the ampersand
[speaker002:] Ah.
[Graham:] now string B four comma zero four no decimals. Okey-doke. Er, over to the left, erm... if you're using file combine copy to copy data across, and you want to copy both numbers and er, labels. There may be some formulae, but you don't want the formulae, how do you do it, the file combine copy. What do you do? There's three steps, I want.
[speaker002:] Well, the way I'd always done it before was, change it to value, before I combined it. But then you
[Graham:] Yes.
[speaker002:] Yeah. When you got
[Graham:] three steps.
[speaker002:] Yeah. Yeah. Oh, is, is it range value.
[Graham:] Ah, well that's one of the steps... [cough]
[speaker002:] you've had it and you combine A
[Graham:] Ah, well that's another method. I'm saying, if you're using file combine copy, because you want numbers as well as labels... Yes, that's the first step, put it on manual...
[speaker002:] Then you do file combine...
[Graham:] Then you do the file combine, yeah...
[speaker002:] And then you do the... range copy range value...
[Graham:] You do range value, do you? Er, and how do you do the range value?
[speaker002:] added value to the field that you're into the field that you are in. You copy it into the field that you're already in.
[Graham:] You copy it to itself. Okay, you can now try. Yes, yeah, there you go. Er, range. Erm... what's the disadvantage of the, the extract method? That is er saving a range from the prompt file, using extract, and then going into the other file and doing a file combine in that extracted file. What's the disadvantage of that method?
[speaker002:] It on things. the extracted file take it to the combined product.
[Graham:] Yes, you er, change the from file, and you save it, but then you forget to do the extract. Th that's the, the risk with it. That's the same problem with your method, by the way. If you use range on the from file to copy it, you may change that file, save and forget to range value to a different range. Right, okey- doke, over to the left. Erm, what doesn't file combine add to copy?...
[speaker002:] Sorry?
[Graham:] What doesn't file combine add, copy.
[speaker002:] Labels.
[Graham:] Labels, is one thing. There's two things.
[speaker002:] Erm Formulas. Formulas.
[Graham:] Formulas, that's it. It doesn't copy labels. Or whatever. Right, the other side. Er, if you create a file linking formulae... in One Two Three Release Two, erm, when you retrieve a file that contains [cough] the file with the formulae, er, does it update the file links, as you retrieve it?... That's the question. Yeah, when you retrieve it, does it update the file links automatically, or do you have to do something to make it update?
[speaker002:] Update it manual. Yeah, I thought you did...
[Graham:] Yes, why I am asking you... or I did I say...
[speaker002:] it does automatic but it wasn't.... Isn't that right?
[Graham:] Yeah, well that's right...
[speaker002:] therefore it was on automatic.
[Graham:] Yes, that's right. It is automatic, in Release Two, but it's not in Release Three, that was the other question. Never mind.
[speaker002:] Oh, sorry [LAUGHTER] two part mistakes.
[Graham:] Across to the er, the left, erm, can you erm, create a file linking formula, that links not just one cell, but a whole range of cells. So you create a range name in the from file that covers [cough] a range of that say ten cells. Erm, does that work?
[speaker002:] No. You can only do one...
[Graham:] Yes, you only link one cell to one cell. That's right. Okey- doke. Erm, in One Two Three Release Three, erm, when you retrieve a file, it doesn't it doesn't automatically update a file. Er, give me two methods of updating... the linking formulae in Release Three or Four. Two methods.
[speaker002:] Does it...
[Graham:] Er, in One Two Three Release Three and Four, it doesn't update the, the linking formulae, when you retrieve the file. Er, give me two methods... for, for how you can update the linking formulae?...
[speaker002:] Would it
[Graham:] No. I'll pass it across. Over here One method? No. No, the one method was to open the other file, the on the prompt file and the two files. You had both files in memory and automatically updates. Yeah. And the other method was to go to the menus and choose, file, admin link refresh. Alright. Erm, over to the er, left erm... how do you make a directory?
[speaker002:] Go into DOS first. Into DOS.
[Graham:] I want to create a directory called put off the root directory. Go into DOS, right.
[speaker002:] Go into DOS backslash C D.
[Graham:] Backslash...
[speaker002:] C D when you can do anything, anything
[Graham:] Right. So what d how do I make a directory put, then...
[speaker002:] M D backslash
[Graham:] Right. Fine. the root directory. Okey-doke. Er, over to the right. [cough] One Two Three and you want to change the current directory, to point at this directory, put. What do you do?
[speaker002:] backslash directory I think you can just type in file.
[Graham:] Yes, file directory, I'll put there then. Okey-doke. Over to the other side, erm. How do you delete all files that have two two in positions three and four, of the file name?
[speaker002:] Delete space question make, question mark, what was it? Two two
[Graham:] Er, twenty two.
[speaker002:] Twenty two, asterisk dot asterisk.
[Graham:] Yeah. That's it. The other side.
[speaker002:] Sorry. Only occasionally.
[Graham:] Erm, when you start testing your spreadsheets, what er, type of numbers should you input?
[speaker002:] Even or round numbers. Round numbers.
[Graham:] Nice ro that's one aspect of it, yes. Round numbers. what do you call a round number?
[speaker002:] A hundred.
[Graham:] A hundred, yeah, okey-doke. Erm, one aspect...
[speaker002:] golden rule
[Graham:] That's it. Yes, that's without a consistent across all [cough] there. Good. Well done. Er, right, over to the other side. Erm, What's an advantage of having your inputs in a separate area, for the purpose of view testing? Erm, what's the advantage of having your inputs in an separate area from the view of testing?
[speaker002:] You can use them again, if you're re-testing.
[Graham:] Yes. Aw use it again, er, yes, can you say a bit more? [LAUGHTER]
[speaker002:] What do you want me to change? a bit more.
[Graham:] Er, you could use them again, that's true, but you could do anywhere, I suppose them again but er,
[speaker002:] But that's why you never put them you put them in numbers.
[Graham:] And that means? Sorry?
[speaker002:] Save them. Save them, extract, yes.
[Graham:] You can save them more easily, than when they're scattered about. Yeah, you can do that. Right, okey-doke. Over to the to the right, erm, give me er three very important parts of the computer documentation?
[speaker002:] the design specifications, is that what you mean?
[Graham:] That's wa that's the overall thing you're talking about is it? No,t the actual... main parts of the documentation.
[speaker002:] Who wrote the spreadsheet.
[Graham:] Because that's detail really, er, I was looking for the main parts.
[speaker002:] What, on the spreadsheet or design the spreadsheet.
[Graham:] Er, off or on the spreadsheet.
[speaker002:] Sort of like, things like, if you've got a, if contents spreadsheet, where it comes from, what files
[Graham:] Er, well, you used, well, you're getting a bit more detailed, but wh what is that thing? Sorry?
[speaker002:] cleared out... having cleared directory
[Graham:] Clear directory. No, perhaps my question was too vague. I wa wanted sort of major pieces of documentations of the individual details on that documentation schedule, major bits.
[speaker002:] The input area. The report to calculations.
[Graham:] Oh, no that's... I guess I'll just have to rephrase my question. Er. Well, what's a spreadsheet map? [LAUGHTER] That's another question. [LAUGHTER] What do you put on a spreadsheet map? That's one of the important of the documentation.
[speaker002:] and then it then it goes down... Yeah, then it goes down to to orgies or whatever [LAUGHTER] what they are [LAUGHTER] has any of that worked?
[Graham:] I don't know, somebody's spreadsheets
[speaker002:] That's three things that are in there.
[Graham:] So wh how do you, what's on the map?
[speaker002:] Erm, come on. you've got squares...
[Graham:] You've got squares...
[speaker002:] You've got writing. [LAUGHTER] [LAUGHTER]
[Graham:] what the lines what the lines showing...
[speaker002:] Showing the cells... the different cells.
[Graham:] Shows you, yeah, you got boxes showing you where things are on the spreadsheets, and you got some tags saying what those are. You got arrows showing flow of data. What else do you have on the spreadsheets?
[speaker002:] Erm, the name of what the, what the erm, spreadsheet looks like.
[Graham:] Er, not in that, well, there might be on that, but er, but that there what resources are on the spreadsheet. On that batch. How are things that were numbered one, two, three, four, five, six...
[speaker002:] Oh, extra process.
[Graham:] Yes, extra processes that are going on. I'll give you er, four for that. [LAUGHTER] well, you didn't get the rest of the question at all. Erm, what... give me erm, give me erm, seven things yeah, seven things to put on this spreadsheet. Seven pieces of documentation actually on this spreadsheet.
[speaker002:] Amendment
[Graham:] That's one, yes.
[speaker002:] Date. What the amendment was.
[Graham:] The date.
[speaker002:] The date, time, file name.
[Graham:] Date, time, file name. Yes, that's two.
[speaker002:] Who created it.
[Graham:] Sorry, who created it. Yes, that's three.
[speaker002:] Run instructions.
[Graham:] Run instructions. Yes, that's four.
[speaker002:] What it's for.
[Graham:] Yes, the purpose of it, that's five.
[speaker002:] File names.
[Graham:] Had that one.
[speaker002:] The date it's been and updated.
[Graham:] We had that one.
[speaker002:] Who updated it. What it
[Graham:] We had that one.
[speaker002:] References.
[Graham:] I suppose you could, but it's not one of the things I had listed. Did somebody say references?
[speaker002:] Yeah.
[Graham:] What did you mean?
[speaker002:] [LAUGHTER] Who do you talk to if you need any information.
[Graham:] Oh yes, that's right, yes reference. That's the right thing. Six. One more...
[speaker002:] Give us a clue.
[Graham:] I've just talked about it.
[speaker002:] Who to talk to?
[Graham:] Sorry? We've just talked about it in this room. The other thing.
[speaker002:] the map.
[Graham:] The map. That's it.
[speaker002:] Well done,
[Graham:] Shall I give them that?
[speaker002:] That's a quarter. Quarter. [LAUGHTER]
[Graham:] I'll give you that, yeah. Right, over to the right, erm... erm, give me another important piece of documentation. Map was one...
[speaker002:] The invoice.
[Graham:] The invoice. I'll pass it across.
[speaker002:] created How about the user manual?
[Graham:] Well, yes, er well... that's one I was after. There's two pieces that are missing. Not including the user manuals. Can't give you that one. [LAUGHTER] Two other useful pieces of documentation.
[speaker002:] What amount.
[Graham:] No, he he's said that one before.
[speaker002:] Is there a design document?
[Graham:] Well, may well be, but er, I wasn't after that... Has anybody think of anything? We only did it er, seven minutes ago, it shows you how quickly you forget. Er, list of the file names, that's one of them, and one of them, open this to everybody, anybody who can get it, gets a point. [blowing nose]
[speaker002:] What directories in it.
[Graham:] No, well, maybe, but er, it wasn't what I was after.
[speaker002:] updated modifications...
[Graham:] Er, well, that's part of what's on the spreadsheet, It's some sort of diagram. Sorry? Not exactly, well, not exactly Diagram representing the things that are in the system...
[speaker002:] folders
[Graham:] Files is that what you said?
[speaker002:] I said folders actually [LAUGHTER] Yeah, files. [LAUGHTER] Well, you already got one
[Graham:] Well, I don't think anybody got it really. There was too many. So let's see, the left got seven, that's nine, and the right got er, three, four
[speaker002:] Who's that for?
[Graham:] Right, thank you all very much for having formulas now.