|
Home > Archive > FoxPro Help and Support > January 2006 > win error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
|
| Hi every one
Recently I made some changes in my application and I now when I try to close
it with a command button in which is cold a release form command I get a
windows error message "name.exe has encountered a problem and needs to
close. We are sorry for the inconvenience.", butt if I close it on the
close button the error message is not displayed. Any clues?
| |
| Lee Mitchell 2006-01-06, 9:27 am |
| Hi fAx:
What version of VFP (and what service pack) are you using?
Have you tried deleting the Foxuser.dbf and Foxuser.fpt file?
Does the error occur in the development environment? If so, trace the code
in the command button to see what line causes the error.
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/gp/lifeselectindex
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003
>Hi every one
>Recently I made some changes in my application and I now when I try to
close
>it with a command button in which is cold a release form command I get a
>windows error message "name.exe has encountered a problem and needs to
>close. We are sorry for the inconvenience.", butt if I close it on the
>close button the error message is not displayed. Any clues?
| |
|
| I'm using VFP 6.0 with sp5 for that application, because it's an old one. I
have tried to delete the Foxuser.dbf and Foxuser.fpt file. When I run the
application thru the debugger the error don't occur. Today I have tried to
start in on another comp. with win. 98 and the error message was:
NAME.EXE caused an invalid page fault in
module VFP6R.DLL at 016f:0c0c2ea2.
Registers:
EAX=00000000 CS=016f EIP=0c0c2ea2 EFLGS=00000246
EBX=0063f968 SS=0177 ESP=0063f948 EBP=0063f978
ECX=00000000 DS=0177 ESI=c0000005 FS=2107
EDX=000e7b9c ES=0177 EDI=0c2f9730 GS=0000
Bytes at CS:EIP:
e9 27 8b f8 ff 57 ff d6 59 e9 b7 cc f9 ff 57 ff
Stack dump:
0c04b98a bff76da8 0040307c c0000005 00000000 c0000005 0063f948 0063f5f8
0063fe28 0c2ed7cd 0c2f9730 ffffffff 0063fd9c 00401635 0063f994 00000001
> Hi fAx:
>
> What version of VFP (and what service pack) are you using?
> Have you tried deleting the Foxuser.dbf and Foxuser.fpt file?
>
> Does the error occur in the development environment? If so, trace the code
>
> in the command button to see what line causes the error.
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
| |
| Lee Mitchell 2006-01-06, 11:25 am |
| Hi fAx:
Take a look at the file version of the VFP6r.dll and VFP6renu.dll files.
Since you are using VFP 6.0 SP5, they need to b version 6.00.8961.00.
Do you have an HP or any type of LaserJet printer driver loaded? If so,
remove all such drivers, regardless of the maker, and try the app again.
If this fixes the problem, take a look at this article:
183522 Divide by Zero error with third-party printer drivers in Visual
FoxPro
http://support.microsoft.com/defaul...kb;EN-US;183522
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/gp/lifeselectindex
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003
>I'm using VFP 6.0 with sp5 for that application, because it's an old one. I
>have tried to delete the Foxuser.dbf and Foxuser.fpt file. When I run the
>application thru the debugger the error don't occur. Today I have tried to
>start in on another comp. with win. 98 and the error message was:
>NAME.EXE caused an invalid page fault in
>module VFP6R.DLL at 016f:0c0c2ea2.
>Registers:
>EAX=00000000 CS=016f EIP=0c0c2ea2 EFLGS=00000246
>EBX=0063f968 SS=0177 ESP=0063f948 EBP=0063f978
>ECX=00000000 DS=0177 ESI=c0000005 FS=2107
>EDX=000e7b9c ES=0177 EDI=0c2f9730 GS=0000
>Bytes at CS:EIP:
e9 27 8b f8 ff 57 ff d6 59 e9 b7 cc f9 ff 57 ff
>Stack dump:
>0c04b98a bff76da8 0040307c c0000005 00000000 c0000005 0063f948 0063f5f8
0063fe28 0c2ed7cd 0c2f9730 ffffffff 0063fd9c 00401635 0063f994 00000001
> Hi fAx:
>
> What version of VFP (and what service pack) are you using?
> Have you tried deleting the Foxuser.dbf and Foxuser.fpt file?
>
> Does the error occur in the development environment? If so, trace the code
>
> in the command button to see what line causes the error.
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
| |
|
|
The file versions are OK, I have tried to build the exe file in VFP 9.0 SP1
and the error does not appear. Can I expect any other problems if I leave it
like this?
On 6-Jan-2006, Leemi@online.microsoft.com (Lee Mitchell) wrote:
[color=darkred]
> X-Tomcat-ID: 703895257
> References: <u01aNvlEGHA.2712@TK2MSFTNGP10.phx.gbl>
> <aUukd9sEGHA.3680@TK2MSFTNGXA02.phx.gbl>
> <e9qTXQtEGHA.336@TK2MSFTNGP14.phx.gbl>
> MIME-Version: 1.0
> Content-Type: text/plain
> Content-Transfer-Encoding: 7bit
> From: Leemi@online.microsoft.com (Lee Mitchell)
> Organization: Microsoft
> Date: Fri, 06 Jan 2006 16:04:24 GMT
> Subject: Re: win error
> X-Tomcat-NG: microsoft.public.fox.helpwanted
> Message-ID: <saROgrtEGHA.1240@TK2MSFTNGXA02.phx.gbl>
> Newsgroups: microsoft.public.fox.helpwanted
> Lines: 62
> NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
> Path: TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA02.phx.gbl
> Xref: TK2MSFTNGP08.phx.gbl microsoft.public.fox.helpwanted:35329
>
> Hi fAx:
>
> Take a look at the file version of the VFP6r.dll and VFP6renu.dll files.
>
> Since you are using VFP 6.0 SP5, they need to b version 6.00.8961.00.
>
> Do you have an HP or any type of LaserJet printer driver loaded? If so,
> remove all such drivers, regardless of the maker, and try the app again.
> If this fixes the problem, take a look at this article:
>
> 183522 Divide by Zero error with third-party printer drivers in Visual
> FoxPro
> http://support.microsoft.com/defaul...kb;EN-US;183522
>
> 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/gp/lifeselectindex
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retired Sept. 30th, 2003
>
>
> e9 27 8b f8 ff 57 ff d6 59 e9 b7 cc f9 ff 57 ff
> 0063fe28 0c2ed7cd 0c2f9730 ffffffff 0063fd9c 00401635 0063f994 00000001
>
>
| |
|
|
I have solved the problem by adding a CANCEL command in to my shutdown
procedure. Is there a way to remove the DO CANCEL... window when the command
is executed?
| |
| Fred Taylor 2006-01-07, 8:24 pm |
| What DO CANCEL window are you talking about? VFP has no such thing. It
must be a user written one called by your ON SHUTDOWN or something like
that.
--
Fred
Microsoft Visual FoxPro MVP
"fAx" <none@server.com> wrote in message
news:eK%23Z736EGHA.1816@TK2MSFTNGP11.phx.gbl...
>
> I have solved the problem by adding a CANCEL command in to my shutdown
> procedure. Is there a way to remove the DO CANCEL... window when the
> command
> is executed?
| |
|
|
I have a small procedure that I call every time the main form is closing,
and on the end of it is:
close all
clear events
quit
.... and now I put the CANCEL instead of QUIT. Now when I close the
application in the right upper corner for a second apiaries a small WAIT
window with DO CANCELED message.
[color=darkred]
>
> What DO CANCEL window are you talking about? VFP has no such thing. It
> must be a user written one called by your ON SHUTDOWN or something like
> that.
>
> --
> Fred
> Microsoft Visual FoxPro MVP
>
>
> "fAx" <none@server.com> wrote in message
> news:eK%23Z736EGHA.1816@TK2MSFTNGP11.phx.gbl...
| |
| Fred Taylor 2006-01-08, 3:24 am |
| Hmm, I've never seen that before. But then, I don't CANCEL, if I'm not
QUITting, I just let the routine do the CLEAR EVENTS and it falls out of my
main code (after the READ EVENTS).
You should have ON SHUTDOWN DO small_procedure
and then add ON SHUTDOWN as the first thing in small_procedure.
ON SHUTDOWN DO small_routine
DO mainmenu.mpr
READ EVENTS
PROCEDURE small_routine
ON SHUTDOWN
CLOSE ALL
CLEAR EVENTS
CANCEL && don't think you need this
--
Fred
Microsoft Visual FoxPro MVP
"fAx" <none@server.com> wrote in message
news:eoBmty9EGHA.644@TK2MSFTNGP09.phx.gbl...[color=darkred]
>
> I have a small procedure that I call every time the main form is closing,
> and on the end of it is:
>
> close all
> clear events
> quit
>
> ... and now I put the CANCEL instead of QUIT. Now when I close the
> application in the right upper corner for a second apiaries a small WAIT
> window with DO CANCELED message.
>
| |
|
|
Thank you all for help, I can just agree that it's strainge.I'll just leave
it like this and try to figure out what's the problem later.
On 8-Jan-2006, "Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote:
[color=darkred]
> Hmm, I've never seen that before. But then, I don't CANCEL, if I'm not
> QUITting, I just let the routine do the CLEAR EVENTS and it falls out of
> my
> main code (after the READ EVENTS).
>
> You should have ON SHUTDOWN DO small_procedure
> and then add ON SHUTDOWN as the first thing in small_procedure.
>
>
> ON SHUTDOWN DO small_routine
> DO mainmenu.mpr
> READ EVENTS
>
> PROCEDURE small_routine
> ON SHUTDOWN
> CLOSE ALL
> CLEAR EVENTS
> CANCEL && don't think you need this
>
>
> --
> Fred
> Microsoft Visual FoxPro MVP
>
>
> "fAx" <none@server.com> wrote in message
> news:eoBmty9EGHA.644@TK2MSFTNGP09.phx.gbl...
|
|
|
|
|