Can I do anything about this error

[Brian Leung]

I am getting an application error:
instruction at 0x00413ec referenced memory at 0x047757fd8
the memory could not be written

What is going on. Given that VB takes care of pointers and memory
management, is there anything I can do about this?

Thanks,

Brian

[Jonathan Wood]

I don't see how anyone could say without seeing the line that caused the
error.

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com
Brian Leung <bleung@zoo.cam.ac.uk> wrote in message
news:393cdad0$1@news.devx.com...
>
> I am getting an application error:
> instruction at 0x00413ec referenced memory at 0x047757fd8
> the memory could not be written
>
> What is going on. Given that VB takes care of pointers and memory
> management, is there anything I can do about this?
>
> Thanks,
>
> Brian

[Jonathan Wood]

I don't see how anyone could say without seeing the line that caused the
error.

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com
Brian Leung <bleung@zoo.cam.ac.uk> wrote in message
news:393cdad0$1@news.devx.com...
>
> I am getting an application error:
> instruction at 0x00413ec referenced memory at 0x047757fd8
> the memory could not be written
>
> What is going on. Given that VB takes care of pointers and memory
> management, is there anything I can do about this?
>
> Thanks,
>
> Brian

[Brian Leung]

That is what I'm asking. It occurs only in the compiled version,
so I do not know how to find the line which caused it. Is there
a way to do so?

Cheers,

Brian


"Jonathan Wood" <jwood@softcircuits.com> wrote:
>I don't see how anyone could say without seeing the line that caused the
>error.
>
>--
>Jonathan Wood
>SoftCircuits Programming
>http://www.softcircuits.com
>Brian Leung <bleung@zoo.cam.ac.uk> wrote in message
>news:393cdad0$1@news.devx.com...
>>
>> I am getting an application error:
>> instruction at 0x00413ec referenced memory at 0x047757fd8
>> the memory could not be written
>>
>> What is going on. Given that VB takes care of pointers and memory
>> management, is there anything I can do about this?
>>
>> Thanks,
>>
>> Brian
>
>

[Brian Leung]

That is what I'm asking. It occurs only in the compiled version,
so I do not know how to find the line which caused it. Is there
a way to do so?

Cheers,

Brian


"Jonathan Wood" <jwood@softcircuits.com> wrote:
>I don't see how anyone could say without seeing the line that caused the
>error.
>
>--
>Jonathan Wood
>SoftCircuits Programming
>http://www.softcircuits.com
>Brian Leung <bleung@zoo.cam.ac.uk> wrote in message
>news:393cdad0$1@news.devx.com...
>>
>> I am getting an application error:
>> instruction at 0x00413ec referenced memory at 0x047757fd8
>> the memory could not be written
>>
>> What is going on. Given that VB takes care of pointers and memory
>> management, is there anything I can do about this?
>>
>> Thanks,
>>
>> Brian
>
>

[Chris Ross]

Try compiling the app with different options. (Native code, P code, etc.) It
seems to me I remember a thread that started off much in the same way this
thread was started. (App only crashes when compiled.)

Other than that, the only thing I can think of is to use line numbers in
your code. Use an On Error GoTo statement before ever procedure, and use the
Erl function to pinpoint the exact line where the app crashes. (Write the
line number in a text file).

Hope this helps.
Chris Ross


Brian Leung <bleung@zoo.cam.ac.uk> wrote in message
news:393d242a$1@news.devx.com...
>
> That is what I'm asking. It occurs only in the compiled version,
> so I do not know how to find the line which caused it. Is there
> a way to do so?
>
> Cheers,
>
> Brian
>
>
> "Jonathan Wood" <jwood@softcircuits.com> wrote:
> >I don't see how anyone could say without seeing the line that caused the
> >error.
> >
> >--
> >Jonathan Wood
> >SoftCircuits Programming
> >http://www.softcircuits.com
> >Brian Leung <bleung@zoo.cam.ac.uk> wrote in message
> >news:393cdad0$1@news.devx.com...
> >>
> >> I am getting an application error:
> >> instruction at 0x00413ec referenced memory at 0x047757fd8
> >> the memory could not be written
> >>
> >> What is going on. Given that VB takes care of pointers and memory
> >> management, is there anything I can do about this?
> >>
> >> Thanks,
> >>
> >> Brian
> >
> >
>

[Chris Ross]

Try compiling the app with different options. (Native code, P code, etc.) It
seems to me I remember a thread that started off much in the same way this
thread was started. (App only crashes when compiled.)

Other than that, the only thing I can think of is to use line numbers in
your code. Use an On Error GoTo statement before ever procedure, and use the
Erl function to pinpoint the exact line where the app crashes. (Write the
line number in a text file).

Hope this helps.
Chris Ross


Brian Leung <bleung@zoo.cam.ac.uk> wrote in message
news:393d242a$1@news.devx.com...
>
> That is what I'm asking. It occurs only in the compiled version,
> so I do not know how to find the line which caused it. Is there
> a way to do so?
>
> Cheers,
>
> Brian
>
>
> "Jonathan Wood" <jwood@softcircuits.com> wrote:
> >I don't see how anyone could say without seeing the line that caused the
> >error.
> >
> >--
> >Jonathan Wood
> >SoftCircuits Programming
> >http://www.softcircuits.com
> >Brian Leung <bleung@zoo.cam.ac.uk> wrote in message
> >news:393cdad0$1@news.devx.com...
> >>
> >> I am getting an application error:
> >> instruction at 0x00413ec referenced memory at 0x047757fd8
> >> the memory could not be written
> >>
> >> What is going on. Given that VB takes care of pointers and memory
> >> management, is there anything I can do about this?
> >>
> >> Thanks,
> >>
> >> Brian
> >
> >
>

[Jim Pragit]

You can write out to a log file to trace your programs execution:

Private Sub MySub
Call LogFile("Entering MySub")

'regular code

Call LogFile("Exiting MySub")
End Sub

where LogFile is some routine you can create to write out a line of text
to a text file. This can help you narrow it down to a particular routine.
Once you know the routine, you can do this for each line of code till you
find the culprit.

- Jim

"Brian Leung" <bleung@zoo.cam.ac.uk> wrote:
>
>That is what I'm asking. It occurs only in the compiled version,
>so I do not know how to find the line which caused it. Is there
>a way to do so?
>
>Cheers,
>
>Brian
>
>
>"Jonathan Wood" <jwood@softcircuits.com> wrote:
>>I don't see how anyone could say without seeing the line that caused the
>>error.
>>
>>--
>>Jonathan Wood
>>SoftCircuits Programming
>>http://www.softcircuits.com
>>Brian Leung <bleung@zoo.cam.ac.uk> wrote in message
>>news:393cdad0$1@news.devx.com...
>>>
>>> I am getting an application error:
>>> instruction at 0x00413ec referenced memory at 0x047757fd8
>>> the memory could not be written
>>>
>>> What is going on. Given that VB takes care of pointers and memory
>>> management, is there anything I can do about this?
>>>
>>> Thanks,
>>>
>>> Brian
>>
>>
>

[Jim Pragit]

You can write out to a log file to trace your programs execution:

Private Sub MySub
Call LogFile("Entering MySub")

'regular code

Call LogFile("Exiting MySub")
End Sub

where LogFile is some routine you can create to write out a line of text
to a text file. This can help you narrow it down to a particular routine.
Once you know the routine, you can do this for each line of code till you
find the culprit.

- Jim

"Brian Leung" <bleung@zoo.cam.ac.uk> wrote:
>
>That is what I'm asking. It occurs only in the compiled version,
>so I do not know how to find the line which caused it. Is there
>a way to do so?
>
>Cheers,
>
>Brian
>
>
>"Jonathan Wood" <jwood@softcircuits.com> wrote:
>>I don't see how anyone could say without seeing the line that caused the
>>error.
>>
>>--
>>Jonathan Wood
>>SoftCircuits Programming
>>http://www.softcircuits.com
>>Brian Leung <bleung@zoo.cam.ac.uk> wrote in message
>>news:393cdad0$1@news.devx.com...
>>>
>>> I am getting an application error:
>>> instruction at 0x00413ec referenced memory at 0x047757fd8
>>> the memory could not be written
>>>
>>> What is going on. Given that VB takes care of pointers and memory
>>> management, is there anything I can do about this?
>>>
>>> Thanks,
>>>
>>> Brian
>>
>>
>

[Jim Pragit]

If you haven't already done so, you may wish to check out these following
articles from Microsoft's Knowledge Base:

PRB: Access Violation in VB Run-Time Using AddressOf
ID: Q198607

FIX: Eight or More ActiveX DLLs in Compiled Project Cause Error
ID: q192653

FIX: More Than One Sub Main May Cause EXE to Crash
ID: Q171555

FIX: Crash When Resizing Column of Split DBGrid
ID: Q168155

You didn't mention which version of VB you were using, so some of these may
not apply.

Also, make sure you've upgraded to the latest service pack. VB6 is up to
SP3.

- Jim

[Jim Pragit]

If you haven't already done so, you may wish to check out these following
articles from Microsoft's Knowledge Base:

PRB: Access Violation in VB Run-Time Using AddressOf
ID: Q198607

FIX: Eight or More ActiveX DLLs in Compiled Project Cause Error
ID: q192653

FIX: More Than One Sub Main May Cause EXE to Crash
ID: Q171555

FIX: Crash When Resizing Column of Split DBGrid
ID: Q168155

You didn't mention which version of VB you were using, so some of these may
not apply.

Also, make sure you've upgraded to the latest service pack. VB6 is up to
SP3.

- Jim

[Brian Leung]

Thanks guys. I'll try these.

Cheers,

Brian

>
>If you haven't already done so, you may wish to check out these following
>articles from Microsoft's Knowledge Base:
>
>PRB: Access Violation in VB Run-Time Using AddressOf
>ID: Q198607
>
>FIX: Eight or More ActiveX DLLs in Compiled Project Cause Error
>ID: q192653
>
>FIX: More Than One Sub Main May Cause EXE to Crash
>ID: Q171555
>
>FIX: Crash When Resizing Column of Split DBGrid
>ID: Q168155
>
>You didn't mention which version of VB you were using, so some of these
may
>not apply.
>
>Also, make sure you've upgraded to the latest service pack. VB6 is up to
>SP3.
>
>- Jim
>

[Brian Leung]

Thanks guys. I'll try these.

Cheers,

Brian

>
>If you haven't already done so, you may wish to check out these following
>articles from Microsoft's Knowledge Base:
>
>PRB: Access Violation in VB Run-Time Using AddressOf
>ID: Q198607
>
>FIX: Eight or More ActiveX DLLs in Compiled Project Cause Error
>ID: q192653
>
>FIX: More Than One Sub Main May Cause EXE to Crash
>ID: Q171555
>
>FIX: Crash When Resizing Column of Split DBGrid
>ID: Q168155
>
>You didn't mention which version of VB you were using, so some of these
may
>not apply.
>
>Also, make sure you've upgraded to the latest service pack. VB6 is up to
>SP3.
>
>- Jim
>