Passing parameters is easy and works basically the same as it does in ASP. Depending on whether you use a POST or GET method from the parent, inside the child page (the one recieving some parameter), you can issue something like:

<%
lcCompany = FOX.GETFORMVAR("Company")
%>

In this case, lcCompany would be a variable which now holds the value of the variable Company passed to the page via a Form POST call.

HTH, but if you are unfamiliar with form POST and GET, let me know and I'll provide more details.

>I wondered about building complex apps. I can easily see how it works when you do everything in one page, but what if what you're doing spans multiple pages?
>
>One thing I'm trying to figure out is how to do a search page. On one page, I can have the user fill in the form and search the table, and give them the first X matches, but how do you give them the next X matches?
>
>Thanks,
>
>Michelle
>
>
>
>>I've been staying away from this thread because I didn't want to appear as if I was hocking my service via UT, but...
>>
>>My server has been running AFP for several months now. AFP is a great product and very stable. I haven't tried WWC so I can't compare the 2 other than to say I have always heard good things about WWC. I have taken a look at the Visual Webbuilder product and it looks like a great tool to use with WWC, something that is definitely lacking in AFP.
>>
>>AFP's strengths are its power and simplicity. I was productive in less than 10 minutes of first trying it. Its drawbacks are I feel like I've stepped backwards to the 2.x days in the way you manage a project. You can use FP and Interdev, no question about it, but it is a scripting engine. But for a large scale web based project (complexity of the app not the size or amount of the data), managing could be difficult.
>>
>>Just my 2 cents.