WWWC has functions that include a paging option which includes "next page" and "previous page" link at the bottom of the response. When we actually pay for it, we'll get source code which might make it possible to hack the function and add new options such as a page number box. I don't know if that source would be in vfp or VC++. For my demo I made another report that does paging manually by storing session variables using other WWWC functions and doing SEEK or GO recordnumber on the recordset before creating the response, which creates basic HTML form controls such as a text box for input of a page number.

>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.