Hi Mike
In our case we were getting the ERROR 78 with SQL.
When debugging why we were getting the error, and that was fun, we found that POSITION was returning long strings. All our KEYS are < 1024 characters in size, so in SQL’s case it seems the problem is not just down to cutting back KEY size.
We decided to increase the size of all variables that were to store POSITION throughout the classes and templates. We didn’t run testing on each scenario but decided that the hammer fix was better than keep trying to debug the issues caused by error 78.
Thankfully since that day we haven’t had many more error 78’s and none of the ones we have had were down to position.
Mark