FIX: Mismatched pushjmp/popjmp Call Error and VFP Closes
ID: Q168056
|
The information in this article applies to:
-
Microsoft Visual FoxPro for Windows, versions 5.0, 5.0a
SYMPTOMS
When attempting to create a new remote connection that has the same name as
an existing remote connection within a database container (DBC), the
following error will occur after choosing cancel in the Connection Designer
Dialog box:
! Mismatched pushjmp/popjmp call.
After this error occurs, Visual FoxPro will close.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. This has been corrected in Visual FoxPro
6.0.
MORE INFORMATIONSteps to Reproduce Behavior
- Issue the command SET SAFETY ON.
- Select New from the File menu.
- Select Project and choose New File. Accept the default name, proj1, and
choose Save.
- Expand the Data folder and select Databases. Choose Add, and add the
database \SAMPLES\DATA\TESTDATA.DBC.
- Expand the testdata folder and select Connections. Choose New.
- In the Connection Designer dialog box, select the Close (X) button from
the upper-right corner.
- In the "Do you want to save " dialog box, accept the offered default
of "connect1" and choose Yes.
- Select Remote Views and choose New.
- In the Select Connection dialog box, choose New.
- In the Connection Designer dialog box, choose OK.
- In the Save dialog box, change the suggested name to the name of an
existing connection, such as connect1, and choose OK.
(NOTE: If SET SAFETY OFF is in effect, then the following steps will not
occur.)
- In the "Connect1 already exists, overwrite it?" dialog box, choose No.
- In the Connection Designer dialog box that you are returned to, choose
Cancel.
- Choose OK when you receive the "! Mismatched pushjmp/popjmp call."
error. Visual FoxPro will close.
© Microsoft Corporation 1997, All Rights Reserved. Contributions by Perry Newton, Microsoft Corporation
Additional query words:
kbvfp600fix
Keywords : kbVFp kbVFp500bug FxinteropOdbc FxtoolCk FxtoolQueryvwdes
Version : 5.0 5.0a
Platform : WINDOWS
Issue type : kbbug
|