>I put a strtofile() command to check if method is being called like you suggested. It definitely is not being called on return trip to server, so method isn't being hit on second trip. The strange thing is page is still returned indicating maybe it is somehow being cached. I switched IIS to expire pages immediately, but to no avail. Weird...

You use the term "return trip" but you probably mean the second hit to the server.

To be sure, it's not a cache issue, do two transactions for your testing. Have one which will call a Response.Write("test") and have another one which will call Response.Write("test2"). Then, start from one and then the other. If cache is an issue, you'll know it immediately. But, at first, firing to test and then test2 will work if cache was an issue. If not, then the problem is elsewhere.

Also, where exactly did you put that STRTOFILE() code?