Thanks for letting me try the Beta and suggest improvements.

Currently the Beta stops when it reaches a "find". What I'd prefer it to do is to carry on searching and populate a list unti it reaches the final date in the set date range. I'd then like to print to a printer or even better a csv file the results so that I can put together a list of outward and return possibilities. At the moment my chosen manual method/way is to work through the BA calender and manually add the availability to a spreadsheet until I come up with an outward and return dates the make a viable trip. KVS would help document that directly to a spreadsheet if a saveable populated list that can be CSV saved. This would present a clear KVS advantage over simply using the BA site.

Even better would be if there was an option to merge lists ie search outward and continually add to a CSV file for say 60 days and then when working on returns use the date in the existing file as the field key and merge the return finds into the already created outward file. To make this clearer, this would mean a date column followed by flight numbers and any other detail for the outward legs followed by the return flights in the following columns. This would then produce automatically what I spend hours working on and would be a real plus for KVS.

The other suggestion is that when the search hits a find it remains on the same date of the find by default. This means that when it stops after finding a flight you have to manually reset the search date for the following day onwards otherwise it just keeps finding the same flight. I'd prefer the default after a hit to be the following day.

I can see substantial advantages if the list making suggestions I made were incorporated but I'm interested to also hear what are the advantages in using KVS in the current Beta form for a power search as against simply using the BA calender?