Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
1929 errors in a grid mousedown
Message
De
16/05/2006 17:14:02
 
 
À
16/05/2006 09:31:12
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Network:
Windows 2000 Server
Database:
Visual FoxPro
Divers
Thread ID:
01121313
Message ID:
01122459
Vues:
17
*** Update:

I believe I have found the culprit.
I have a filter expression set on a table used by that form that involves a property of the form. I discovered the connection by accident while testing something else, but if you try to browse that table in the IDE you get error 1929. If I remove the 'thisform' reference from the filter expression and make a work-around for that, my troubles may cease.


Here's the actual error in its latest form:
Error number:       1929
Error message: THISFORM can only be used within a method.
The error occurred in : dd.pageframe1.page3.grid1.MouseDown
Line #  :          0
Info from testing, and further investigation:

I found no dynamic properties set in that grid.

The 'Mousedown' event is not overridden with event code in any control on the page, the grid, or the form.

The 'click' event is not overridden on the page, pageframe, form, or any part of the grid.

I set my form up to test in the IDE, and when this error happens, I see a msg in the status bar that says 'Filter Cleared'

I looked for all occurences of 'SET FILTER' and there are only a few, none of which are in any event code fired by clicking a control.

*The only place I issue a 'SET FILTER TO' command, to clear a filter on a table is in a button on a different page. This is part of a 'find' function I was experimenting with that could be disposed of entirely, if needed. I wonder if I disabled that button ... ?

My impression is that something is corrupted in the scx. The last time I had this type of problem, it was to do with a combo box that I later recreated from nothing to try to get rid of the problem.


Steps Taken:

1. I followed Peter's advice and moved all the classes from the vcx they were in to a new empty one and renamed it to the production vcx file to create a clean one. - No effect, though it probably was beneficial to do.

2. Backtracked up the class hierarchy looking for suspect event code. I have not found any yet.
Jim Newsom
IT Director, ICG Inc.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform