Access violation in module Tee7C6.bpl

Pavlo Savchyn · Post by **Pavlo Savchyn** » Mon Jun 04, 2007 9:04 am

We use TeeChart Pro 7.0 VCL/CLX version. During zooming "Access violation at address 013063EA in module "Tee7C6.bpl". Read of address 0EB70001" message have been appeared. Can you tell something about this issue? (as fast as possible)
Thanks in advance.

Narcís · Post by **Narcís** » Mon Jun 04, 2007 9:18 am

Hi Pavlo,

I'm not able to reproduce the problem here using TeeChart Pro v7.07 VCL, which is the latest version available at the client area. Which exact TeeChart version are you using?

If you are using v7.07 and the problem persists, could you please send us a simple example project we can run "as-is" to reproduce the problem here?

You can post your files at news://www.steema.net/steema.public.attachments newsgroup or at our upload page.

Thanks in advance.

Pavlo Savchyn · Post by **Pavlo Savchyn** » Mon Jun 04, 2007 9:32 am

We are using TeeChart Pro 7.0
and working with big array of data.
Could you tell me about data limits and other issues related to this version of TeeChart?

Narcís · Post by **Narcís** » Mon Jun 04, 2007 9:37 am

Hi Pavlo,

There's no data limit in TeeChart except for your machine's memory. At v7's release notes you'll see what has been implemented and fixed on each v7 maintenance release.

Also notice that v7.07 is freely available to all v7 registered customers.

Pavlo Savchyn · Post by **Pavlo Savchyn** » Mon Jun 04, 2007 9:59 am

Unfortunately I can't send you files because this access violation happens very rarely and its hard to describe the concrete scenario. But may be you can find something using the address value...
Thanks in advance.

Narcís · Post by **Narcís** » Mon Jun 04, 2007 10:07 am

Hi Pavlo,

Even we were able to find where the error happens we should be able to debug it to see when and why it happens. So any set of instructions or project showing how to reproduce the problem here would be very helpful.

Thanks in advance.

Pavlo Savchyn · Post by **Pavlo Savchyn** » Mon Jun 04, 2007 11:35 am

This bug has been revealed by our customer and, unfortunately, we can't reproduce it. May be you give us any recommendation to walk around this problem...