>Those are totally different issues that have to do with Web design and not with FoxISAPI or how it works. IOW, you'll need to do your homework a bit in order to work through these issues.
>
>Building your first application in Frames is a bad call to begin with, because Frames require extra management and synchronozation.
>
>+++ Rick ---
>
>
>>>>1. Does that mean that Foxisapi which comes with VFP does not work at all?
>>>>AT least that's is my impression.
>>>
>>>No, it works. It's not easy to get working and you basically have to build your own framework for it. I personally have not used it for anything but a few projects where it was a requirement, but it definitely works fine.
>>>
>>>>2. I am still not sure that isapi is the best technique to use. That's why I just wanted to test another Web connector with my apps.
>>>
>>>ISAPI is a connector application API. Just about every tool that works with IIS is implemented as an ISAPI extension. THis is includes Active Server Pages, Cold Fusion, FoxISAPI, Active FoxPro Pages, VB's Web Classes (which actually use ASP+COM) and Web Connection.
>>>
>>>You need to make a decision on whether you want to use scripting or a more code centric approach.
>>
>>Hi Rick,
>>It is really hard to argue with you when it comes to Internet. And I am not going to. All I want is to understand why a simple frame with two pages each is calling same form same method never works for me? Second page is always timed out. Also if I dont release foxisapi efter every hit I see some caching problems.
>>Thanks, Mark
OK, forget about frames shmames. Simultaneous calls from two computers to the same class.method never work for me. Also if I dont release foxisapi efter every hit then sometime forms come with no data. An immediate call to that form brings it with data.
Thanks Mark