Customer Support -- Bugs

If you're experiencing a problem with one of our software products, please fill out and submit the following bug report form. You may also want to check out our list of known problems.

If what you want to tell us is really more of a suggestion or a request for enhancement, please use our suggestion form instead.

Bug Report Form

When you submit your bug report, it will be entered into our database for tracking purposes. It will be associated with the account name under which you accessed this web. After an initial assessment by our support department, the resolution of the problem will be assigned to an appropriate engineer. Periodically we will post notices regarding bugs reported by our customers in the Known Problems section of this page, and tips or workarounds on the FAQ page.

Please be as specific as possible when describing the problem.

What version of the software are you using?

What operating system are you using?
Other:

Please enter a brief one-line description of the problem:

(example: "Editor doesn't respond to up-arrow under image")

If the problem is reproducible, please list the steps required to cause it,
leaving a blank line between steps:

(example: "1. Create a new file. 2. Insert some text ...")

If the problem is not reproducible (only happened once, or occasionally for no apparent reason), please describe the circumstances in which it occurred and the symptoms observed:

(note: it is much harder for us to fix non-reproducible bugs)

If the problem causes any error messages to appear, please write down the exact text displayed and enter it here:

Please provide us with the following information in case we need to contact you:
```
Name:    
Phone:   
E-mail:   
```

We may need to contact you for more information, such as if we have trouble reproducing the problem you describe.

Back to Top

Known Problems

The following is a list of some known problems with our software; we are working to correct them for the next release.

VERSION 1.0 BUGS

1. Set Conn = Nothing generates run-time error - When clearing out the variable holding your QBConnection object, if the CloseConnection method has already been called, run-time error '-2147220468 (8004040c)' ("Begin Session" method has not been called or did not succeed) is sometimes generated. This is a problem with CoreObjX trying to terminate the connection to QuickBooks twice. The problem has been fixed and will be available in the next build. (12/17/2001)

2. Encounters 'Internal error 2762' at end of Install on Windows XP. This is an error with InstallShield, the installation development tool used to create our installation packages. As of now, this error does not have a resolution, though we do have an issue in with InstallShield and we're waiting on their response. It should be noted that, even though the ending dialog implies that the installation was interrupted, CoreObjX is actually installed on the target machine and functional.

3. TimeTrackings that are billable to a customer cannot be created. They will produce and XML Parser error. There is a patched DLL available on the Downloads page that corrects this problem.