Pretty close.

>Create a memory variable working area for each field.

Yes. The local just declares that the varibles we will be using is local to this method. (nothing else can access them and the are release when the method is finished)

>Then relate the variables to the text fields within the form.

Yes. The first section just copies what is currently in the text boxes to memory variables.

>Then open the databases and fields.
>then relate the variables to the fields within the databases.

Yep. The SQL select statement will use the where clause to pull just the matching records in the tables into a new cursor.

> This part I don't understand INTO CURSOR ReportPreview ?

I'm not sure how you set up your reports. An easy way to do it is create a cursor that only contains the data you want to report. Then create your report to show that data. The INTO CURSOR clause of SELECT just tells it to dump the results into a cursor (a temporary table). I called the cursor ReportPreview. You can change the name to anything you want. Look up SQL select in the help for more info.

>Is ReportPreview the name of the report ?

Nope. ReportPreview is just a cursor. You'll need to create a report that would use the ReportPreview cursor.
>
>Then test for querie for results.
>
>if .T. print preview
>if .f. Return message.

Exactly