Visual FoxPro Programming - memory could not be read

Author

memory could not be read

rajani

2005-05-16, 9:00 pm

Hi friends
When closing our application we are getting the error message "The
instruction at "0x18004160" referenced memory at "0x18004160". The memory
could not be "read"".

This happens sporadically when closing our app. It is getting really
annoying. I have been looking on the internet for possible solutions but I
have yet to see a similar message where the instruction location is
referencing the memory at the same location. It occurs on more than one
machine and the memory reference is always the same.

Any ideas on this much appreciated.
Thanks
--
cheers

David Frankenbach

2005-05-17, 4:02 am

Ranjani,

What version of VFP? What does your app shutdown code look like?

--
df - Microsoft MVP FoxPro http://www.geocities.com/df_foxpro

"rajani" <rajani@discussions.microsoft.com> wrote in message
news:903CC22C-EFC8-40F4-B5CC-22D69D1A3599@microsoft.com...
> Hi friends
> When closing our application we are getting the error message "The
> instruction at "0x18004160" referenced memory at "0x18004160". The memory
> could not be "read"".
>
> This happens sporadically when closing our app. It is getting really
> annoying. I have been looking on the internet for possible solutions but I
> have yet to see a similar message where the instruction location is
> referencing the memory at the same location. It occurs on more than one
> machine and the memory reference is always the same.
>
> Any ideas on this much appreciated.
> Thanks
> --
> cheers

rajani

2005-05-17, 4:02 am

Hi David
we r using vfp8 and sp1.

it closes all open forms and runs following code
IF !glDevelop
PUBLIC glQuit
glQuit = .T.
ENDIF
CLEAR EVENTS
SET SYSMENU TO DEFAULT
POP MENU _MSYSMENU TO MASTER
IF TYPE ('tbrMain.name') = 'C'
RELEASE tbrNav
RELEASE tbrMain
RELEASE tbrSnapShot
RELEASE tbrSnapShot1
ENDIF
IF !glDevelop
SET NOTIFY OFF
ENDIF
IF !glDevelop OR !FILE('start.prg')
QUIT
ENDIF

here glDevelop tells whether it is runtime or develop
"David Frankenbach" wrote:

> Ranjani,
>
> What version of VFP? What does your app shutdown code look like?
>
> --
> df - Microsoft MVP FoxPro http://www.geocities.com/df_foxpro
>
> "rajani" <rajani@discussions.microsoft.com> wrote in message
> news:903CC22C-EFC8-40F4-B5CC-22D69D1A3599@microsoft.com...
>
>
>

Lee Mitchell

2005-05-17, 9:01 pm

Hi Ranjani:

Have you tried adding a SYS(1104) function before calling the QUIT? Also,
if you are closing a lot of tables, you might want to look at using
SYS(3050) function. See
http://support.microsoft.com/defaul...KB;EN-US;176483

Along those lines, have you deleted and recreated any index files you have
on your tables? Finally, you mention you have VFP 8.0 SP1. Make sure the
VFP runtime files (VFP8r.dll and VFP8renu.dll) are SP1 (version 3117).

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 HAS ARRIVED!! --*
Read about all the new features of VFP9 here:
http://msdn.microsoft.com/vfoxpro/

*--Purchase VFP 9.0 here:
http://www.microsoft.com/PRODUCTS/i...cid=54787e64-52
69-4500-8bf2-3f06689f4ab3&type=ovr

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003

>Hi David
>we r using vfp8 and sp1.

>it closes all open forms and runs following code
>IF !glDevelop
> PUBLIC glQuit
> glQuit = .T.
>ENDIF
>CLEAR EVENTS
>SET SYSMENU TO DEFAULT
>POP MENU _MSYSMENU TO MASTER
>IF TYPE ('tbrMain.name') = 'C'
> RELEASE tbrNav
> RELEASE tbrMain
> RELEASE tbrSnapShot
> RELEASE tbrSnapShot1
>ENDIF
>IF !glDevelop
> SET NOTIFY OFF
>ENDIF
>IF !glDevelop OR !FILE('start.prg')
> QUIT
>ENDIF
>

>here glDevelop tells whether it is runtime or develop
>"David Frankenbach" wrote:

> Ranjani,
>
> What version of VFP? What does your app shutdown code look like?
>
> --
> df - Microsoft MVP FoxPro http://www.geocities.com/df_foxpro
>
> "rajani" <rajani@discussions.microsoft.com> wrote in message
> news:903CC22C-EFC8-40F4-B5CC-22D69D1A3599@microsoft.com...
memory[color=darkred]
but I[color=darkred]
>

David Frankenbach

2005-05-18, 4:06 am

Ranjani,

Do you have an error handler still in effect that could catch any late
shutdown errors that might be happening before the memory access error
happens? Are you sure all your data sessions are closed down with no pending
TableUpdates?

--
df - Microsoft MVP FoxPro http://www.geocities.com/df_foxpro

"rajani" <rajani@discussions.microsoft.com> wrote in message
news:5358607B-6880-4612-BD3D-12886E7A226A@microsoft.com...
> Hi David
> we r using vfp8 and sp1.
>
> it closes all open forms and runs following code
> IF !glDevelop
> PUBLIC glQuit
> glQuit = .T.
> ENDIF
> CLEAR EVENTS
> SET SYSMENU TO DEFAULT
> POP MENU _MSYSMENU TO MASTER
> IF TYPE ('tbrMain.name') = 'C'
> RELEASE tbrNav
> RELEASE tbrMain
> RELEASE tbrSnapShot
> RELEASE tbrSnapShot1
> ENDIF
> IF !glDevelop
> SET NOTIFY OFF
> ENDIF
> IF !glDevelop OR !FILE('start.prg')
> QUIT
> ENDIF
>
>
> here glDevelop tells whether it is runtime or develop

rajani

2005-05-19, 4:02 am

Hi Lee
Thanks for post.
Yes ,all runtime files are in sp1 .
and regarding link ,i noticed that these errors do occur on the machines
with normal RAM(i mean 256 mb).
unfortunately it happens intermittently and difficult find out when and what
causing these.

meantime i'll sys(1104) function.
--
cheers

"Lee Mitchell" wrote:

> Hi Ranjani:
>
> Have you tried adding a SYS(1104) function before calling the QUIT? Also,
> if you are closing a lot of tables, you might want to look at using
> SYS(3050) function. See
> http://support.microsoft.com/defaul...KB;EN-US;176483
>
> Along those lines, have you deleted and recreated any index files you have
> on your tables? Finally, you mention you have VFP 8.0 SP1. Make sure the
> VFP runtime files (VFP8r.dll and VFP8renu.dll) are SP1 (version 3117).
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 HAS ARRIVED!! --*
> Read about all the new features of VFP9 here:
> http://msdn.microsoft.com/vfoxpro/
>
> *--Purchase VFP 9.0 here:
> http://www.microsoft.com/PRODUCTS/i...cid=54787e64-52
> 69-4500-8bf2-3f06689f4ab3&type=ovr
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retired Sept. 30th, 2003
>
>
>
>
> memory
> but I
>
>
>

rajani

2005-05-19, 4:02 am

by the way i got the same error again even after adding sys(1104).
looks like i need to dig little more :(
--
cheers

"Lee Mitchell" wrote:

> Hi Ranjani:
>
> Have you tried adding a SYS(1104) function before calling the QUIT? Also,
> if you are closing a lot of tables, you might want to look at using
> SYS(3050) function. See
> http://support.microsoft.com/defaul...KB;EN-US;176483
>
> Along those lines, have you deleted and recreated any index files you have
> on your tables? Finally, you mention you have VFP 8.0 SP1. Make sure the
> VFP runtime files (VFP8r.dll and VFP8renu.dll) are SP1 (version 3117).
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 HAS ARRIVED!! --*
> Read about all the new features of VFP9 here:
> http://msdn.microsoft.com/vfoxpro/
>
> *--Purchase VFP 9.0 here:
> http://www.microsoft.com/PRODUCTS/i...cid=54787e64-52
> 69-4500-8bf2-3f06689f4ab3&type=ovr
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retired Sept. 30th, 2003
>
>
>
>
> memory
> but I
>
>
>

Sponsored Links