>>Hi Bret,
>>
>>My suggestion would be to prompt the user for the value needed yourself via textbox, combobox, etc. Then when you have the value then open the view. I NEVER let the default VFP prompt come up for parameratized views in my apps. HTH
>>
>>>I have a view that has a prameter. The user gets prompted to put in the value and press OK, but there is also a cancel button. When the user presses this it generates an error that causes my application to abort (basically generate an errorlog entry and quit). Is there a way I can use a parameterized view without a cancel button coming up or does anyone have any ideas on how to trap the error that the cancel button causes before my error trapping routines kick in. Any help would be appreciated.
>
>In the next version of VFP there will be a function similiar to messagebox called I think inputbox. This will give us the capability of getting input from a user with what ever prompt we want. They talked about it at the Southern California conference a couple of weeks ago. This would be ideal for my view needs, but for now we need a prompt to come up and not clutter a screen with extra input fields.

How about creating your own modal form class that will contain a textbox to enter value and an OK or OK and Cancel button(s)? Make the form return the .Value of the textbox and use the value for the view.