>My boss has told me that I'm good to go for your training end of this month. Boy do I need it!>

Sounds great! It promises to be a good class. At any rate, you're just in time since the registration cutoff date is Friday! Also, I recommend that you bring your application with you on a laptop so I can more easily answer your app-specific questions (I stay a bit after class for this sort of thing).

As an aside, you CAN specify the type of your view parameters programmatically by using the DBSETPROP command's ParameterList clause (the syntax is listed in the VFP help file under DBGETPROP). It's basically as follows:

DBSETPROP("lv_MyView", "View", "ParameterList", "vp_cParm1, 'C'; vp_iParm2, 'I'")

As you can see, the parameters are listed in a string separated by a semicolon.

>Now what business object do I use for a multi page (3) look up business object. Page 1 is a text box to get the Customer's Number from a view of all customers. Page 2 is an open orders grid. Page 3 is a shipped grid. From each of those pages there will be command buttons that display more detail as needed by the operator.>

Without knowing all the details, it's difficult to give you a truly complete answer, but basically, you can place a Customer Lookup business object on page 1. It sounds as if subsequent pages will each have their own business object on them which should be children of the primary business object on page 1.

For an example of this, check out the sample Project Manager's ProjectsForm...it sounds somewhat similar to the architecture you describe. There's also information in the Mere Mortals Developer's Guide on setting up business object relationships.

Regards,