Hi!
Please, take a look to the Thread #
569629. Maybe you will figure out something from there. If you will find what cause a problem, let us know. I did not replied to this thread because I do not have VFP7 yet. However, in that thread problem occurs also in the VFP6SP5, that I'm using now. If you can, please, send me a project or that form so I will try to reproduce this behavior here and tell for sure what is wrong with that.
>We have just started using VFP 7.0, and have stumbled onto a really strange situation:
>
>1. I built a form that included a grid with 10 columns. In the DblClick method of the Text1 control in each column I put code to call the DblClick method for the grid itself (THIS.Parent.Parent.DblClick). I tested the form, and the grid works just fine.
>
>2. I created a new form, copied and pasted the grid from the first form onto the new form, and tested the new form. When I tried to use the DblClick in Column #1 it failed. I checked the grid, and the code is still in the DblClick method.
>
>3. Upon further research I discovered that the grid on the second form now has a Column0, which I have never seen before. I checked in Design Mode, and the columns were named correctly, i.e. Column1 through Column10. Thinking the control itself was bad, I deleted it and tried to put a new grid on the form. After testing, I discoverd that this new grid also had a Column0. So it appears that there is something on this new form that is causing the grid to change.
>
>4. Can anyone shed some light on this?
>
>Bryan A. Jackson
>for Rudy Nieves
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.