>>>>2) Is there an error handler in the program that identifies the line of code wher the program fails?
>>>
>>>There is an error handler running for the whole program suite, but it doesn't fire. As I said, the sys just falls over and dies.
>>
>>Hmmm, that will be fun to diagnose. How'bout resending and reinstalling the package? For a 'this is the only site having the problem' situation, it seems like a reasonable thing to try, unless there is some obviously unique situation about that particluar computer.
>>
>>Enjoy! :-)
>
>Aye
>
>Sergey has suggested that it may be corrupt data; I've suggested to my colleague that he try reindexing the relevant tables and sending again. 'S up to him now (I get to miss out on the enjoyment :-)

Seeing it's a FPD2.6 thingy, and the way it crashes - maybe the memory settings were just wrong for legacy tasks on that machine? Why don't you try running it from within DosBox? It may provide a safer environment, and maybe even report the type of fault.

BTW, thanks again for pointing me to DosBox - I got a couple of good old games from the nineties which work just great in it :).