>Well, I don't share your opinion, since the view DOES work within VFP 8 (when created in VFP7). The bug is that the checking mechanism thinks the macro substituation is a syntax error, while it is not.
>

I see the following:

In VFP7 -

1. You can create a view with the &?var syntax
2. If the variable exists, the view can be USEd.
3. If the variable does not exist, you are prompted to enter a value for the variable in the parameter input box. I can't figure out how to enter any value that does not return a syntax error. Even .T. fails.
4. Other than the prompt dialog if the variable does not exist (which I can't figure how to make work anyway), I get the same behavior with &varname as with &?varname.

In VFP8 -

1. You get a syntax error creating a view with the &?varname syntax.
2. You can create a view with the &varname syntax.
3. Functionally, &varname works the same as &?varname did in 7, other than the prompt which I can't get to work in VFP7 if the variable does not exist.

Looks to me like you can get exactly what you want by removing the ?.
BTW, I've never seen the syntax with the & and ? combined until today.

>
>>Did you get any bug confirmed by MS? What are the bugs found?
>
>Two of my reported bugs have been confirmed:
>BUG: Object with negative .left proptie still visible Thread #751331 Message #751331
>BUG or feature: Transparent checkbox not transparent Thread #751821 Message #751821

I see both of these. I'm not convinced the .left behavior is a bug, as some people may want all objects to be visible at design time. This happens in VFP7 and VFP6 also. If you want to hide the object, you can set the left or top property to a high positive or negative value, say -2000.

The checkbox issue is a bug, but it's not a transparency problem. The backstyle = transparent is not applicable to graphical checkboxes. The problem is that backcolor is incorrect if the graphical checkbox is placed on a pageframe page, the checkbox assumes the backcolor of the form rather than the page. This happens if the checkbox is style=graphical, and Specialeffect = Plain or Hot Tracking. This happens in VFP7 also. VFP6 does not have Specialeffect = Hot Tracking, but it does not happen in VFP6 with Specialeffect = Plain.

>I confess that they're not that serious but the other bugs:
>Poor picture quality in VFP & Terminal Server Thread #751827 Message #751827
>BUG: visual side effects with native gridbar Thread #750841 Message #750841
>Are more irritating in that it has negative effects on how the user interface is shown to the user.

I looked at the above threads, and there isn't enough information for us to see what is going on. If you can provide additional details including steps to reproduce the behavior we can have a look at those. A sample image file that demonstrates the behavior for the picture quality issue would be helpful. You can email me directly if you like.