Hmmm - interesting. CR APIs do not throw this error. At least I've never, ever seen this error my self, or have I ever seen it reported before. In any case, it should be Accpac asking us as it is an issue in their software. If, with their cooperation we determine that this is a CR issue, we can work ion resolving it. Like I said before, as it is, I have no idea how Accpac implements the CR APIs or the CR Service Pack they are using in their app.
What we have here is akin to you driving your car to your mechanic and asking him to fix the noise coming from the engine. But the hood is sealed so the mechanic can't even determine if the engine is 4, 6 or 8 cylinder... Apologies for the analogy, but it works 
(?).
- Ludek