Further information: When running 10.3.1.4 on the client, the error does not occur (even though the server is still 10.4.1.3.)
As I can't reproduce it with a database created on 10.3.1.4, it could be that the database itself is older than that, so I'm currently working back through the versions to see if I can make it happen with an older one. Daniel
