Dry and warm (14°C) in the morning with just enough and the right kind of clouds to show off in long red bands while the sun laboriously climbs over the horizon. And it stays that way until after 20:00 when a slow rain descends.

Theo had a discussion planned in the morning about passing over the TOS2000 system from the Progress people to Ronny and me. This should be done somewhere in September.
Sasha, one of the developers from Progress doing the TOS2000 programming (lead developer actually) had a small problem so we had to go and help him on a bit. Ronny has been doing that all week but this time he needed me because the problem seemed to lay on the AS/400 side. Well it wasn't but logging the communication coming on the AS/400 we found the problem. Something with a before and an after transaction trigger. A quick and dirty solution was possible but Q'n D solutions have a habit to bite back later and later could be when the current developers were gone so that we would have to solve it we pushed for a good definitive solution.
And we got that, at the cost of extra work for Sasha. <eG>

Afterwards (afternoon) we had the planned discussion. Which did not lead to a conclusion but it did cause Theo to notice some upcoming problems that were not (yet) on his horizon.

And then, to stay in style, the Belgians pulled another stint.
During week 25 to 29 I worked on a correction program for the problem with archived orders in status VAL. A very tricky program to test. I also adapted the actual archiving program to prevent the problem from recurring.
The danger was that the new archiving program, when run before the correction program would irrevocably destroy the records needing correction. Upon delivery I added a description of how the programs should be used, explicitly stating (twice) that the correction program had to be run before installing and using the corrected archiving program. Later the operator, Robert, from Belgium called and I walked him trough the process on a copied set of data. All went well.
Now guess what they did? On they active production database.
Ha, I see, nobody needs a second guess.
So now they lost their data and there is no way to get it back without destroying several days worth of work.

It's like giving someone a hand grenade with the instruction, in 24 point Arial, to 'pull out the pin and throw the grenade'. And then seeing them throwing the pin.

Adios