Rich;

It is amazing what a simple question will lead to. So here are a few thoughts from me.

As in many things in life what you want to do is up to you. When it comes to anomalies (bugs) with Visual FoxPro, we see the passion of the community speaking. We tend to express our frustrations and do nothing about it except upset others and ourselves. What we need is a plan of action and follow through.

Now we can treat this subject in many ways such as:

1. Be quiet – say nothing.
A. That does not seem productive.

2. Scream and jump up and down.
A. That still does little good but may be good exercise.

3. Use the Microsoft system.
A. Something needs to be improved here sports fans!

4. Bombard Microsoft with thousands of bug reports on the same problem.
A. That might get attention or shut down the “system” from overload!

5. Use the Wiki, UT or both to report bugs, info Microsoft and Microsoft reports back on status.
A. There are many developers who do not use the Wiki or UT.

Well there is no perfect system and we do not make the business rules for Microsoft. We should get our collective act together and use it for something positive. Hiding our heads in the sand and expressing our frustrations to each other are two approaches. Now let us do something productive and contact the people we know at Microsoft and let them know how we feel!

Tom





>In VFP 6 if you place a comment at the top of a method in class and then drop the object onto a form, when you add code to the method the classes’ parameters are/were automatically placed at the top of the method.
>
>Now in VFP 7 the parameter list only appears if the classes’ parameter list (the LPARAM statement) is the first line. Anyone figure out a way to get around this bug?
>
>Example Class Method in Photo Control
>
> PROCEDURE deletephoto
> ******************************************
> * Deletes Attached Photo
> ******************************************
> LPARAMETERS tlForce
> LOCAL lcPhotoFile
> * Get photo path and file
> lcPhotoFile = THIS.GetPhotoFileName()
> * Check to see if the file exists
> IF FILE(lcPhotoFile)
> * Confirm Deletion
> ELSE
> * No photo file found to delete
> ENDIF
> ENDPROC
>
>Place the Photo Control on a form and open the DeletePhoto method. No parameter list. Delete the comments at the top, now you get the list.
>
>This one cost me some time!
>
>Rich