Very unlikely that this has anything to do with FoxISAPI. Most likely has do to with the way the framesets are set up - each browser can be very picky about the frame syntax. For example, if you leave out a /FRAME tag some browsers will figure it out but some won't.

Best bet is to create some dummy pages with the frameset configuration you want and some very simple HTML and get that to work first.

Why don't you post the skeletons of the frameset and the various pages that are supposed to populate targets, minus the FoxISAPI stuff, and maybe I (or someone else on the thread) can figure it out.

>>I have an application that works as follows. The page is divided into 4 frames. In frame1, we have the alphabet, each letter is a hyperlink.
>>
>>When the user clicks on a letter in frame1, frame2 is populated with all categories in the catalog that start with that letter. Each category is a presented as a hyperlink.
>>
>>When the user clicks on a category, frame3 is populated with all products in that category.
>>
>>When the user clicks on a product, the description shows up in frame 4.
>>
>>The hyperlink for a letter looks lis this:
>>
>>

<a href="scripts/foxisapi.dll/dcc.headings.runit?headletter=A" Target="frame2"> A </A>

>>
>>In IE5, this works great. The FoxISAPI gets the listing and puts it into frame2.
>>
>>In NS4.61, it opens a new window and nothing displays.
>>
>>In IE4, nothing seems to happen.
>>
>>Has anyone seen anything like this before? What could be the problem?
>
>My hyperlink text didn't quite show up right. Here it is (minus the open and close brackets so it shows up as code rather than the actual link).
>
>

>a href="scripts/foxisapi.dll/dcc.headings.runit?headletter=A" Target="frame2"> A </A
>