Jim,

Your parameters are memory variables in the Init event that will go out of scope when the init event ends. The best way to handle this is to create a form property for each parameter you'll need to access outside of your init. In the init assign each parameter to its corresponding property. Then from your command button events you'll be able to access the form properties using THISFORM.MyProperty.

>I continue to have problems with the basics, this time passing parameters.
>
>I probably am not doing this correctly and would appreciate guidance if needed. I have a bunch of FPW tables and am creating an interface to query them using VFP3. There are three bits of search information that may be supplied, and 2 bits (date range) that are required. Using the info supplied a search is done and results are written to a separate table. A form is called displaying the gathered information in a grid. At this point I would like to be able to print a report of the query (if desired by the user) using a button pick.
>
>Here's my problem, I would like to have the search parameters displayed on the report. I pass the information from the search routine to the INIT method of the results form. They get there but I'm unable to access them beyond that. Once the parameters get to the form how do I access them at the command button and report level short of making them public?
>
>Thanks.