One of the users of our software reported receiving "Error 1103 - Invalid Seek Offset".
Help file says only to contact Microsoft - no additional info. So, I did a search here and there doesn't seem to be any one reason for this error. One suggestion was to re-index all tables, another was that it could have something to do with the Client32 for Netware (they are running Novel).
Luckily we have built a function to re-create the index files - hopefully that will solve the problem (haven't heard back from them in the last 1/2 hour...)
However, can anyone shed any light on this error? Has anyone determined specifically what causes this error?
Al Williams
Anola MB, CANADA