If you found a problem or bug in one of our products, first of all try to reproduce your problem in a brand new project you can send us to demonstrate the issue. Our experience tells us that such a sample is required to process your request at least in 80% of cases.

First, we need this code to launch it on our development pc's to see the problem itself and properly classify it. If it is a bug in our product, we also need this code to work with it under the debugger. Don't send us a general description like "this method doesn't work" or something like that, and then wait (and lose) about one business day for a letter from us in which we ask you to send us a sample.

Second, it would be nice to see a detailed description of the problem with a sequence of actions of how to reproduce it. The only exclusion to the previous advice could be the case when the problem with our component can be reproduced in a brand new project, and you tell us how to do that step-by-step.

Third, don't forget that a picture is worth a thousand words, and if possible, send us one or two screenshots of your problem too.

And the last, but not least. The problem can be specific only for some cases, so report the full version of the used component (major, minor, build numbers; its platform - ActiveX, .NET, etc) and your development environment (OS version, its 32/64-bit status, main installed components such as IE, MS Office, .NET Framework and service packs).