Theres is some good info here:
http://64.233.187.104/search?q=cache:eFf0D6su47wJ:www.calvinhsia.com/default.asp%3FPage%3Dlink%26file%3Dpapers/AdvancedVFPServers.mht+Calvin+Hsia+%22Advanced+Visual+Foxpro+Servers%22&hl=en&lr=&strip=0

Calvin Hsia "Advanced Visual Foxpro Servers" (It's hard to get a clean copy - I got my last from Claude Fox's site)

I have a project using a VFP server (ISAPI). It works great.

One issue that has been discussed before is the fact that most systems on which your server will reside will only have one processor. So mutlti-threading, at least in some conversations I've heard, may not be everything it seems.

What you want, I think, is to not have to open (USE) a DBF every time the server is instanciated. THATS WHAT WE ALL WANT!:-). If you come across a way to do this - please let us know.

One way you can optimize server requests - is to open the files (DBF) as read only (or NOUPDATE) if a write back is not required. You can also only open the files a particular method requires, rather than all the server may have access to.

The paths can be hardcoded into a server property or you can use relative pathing with:_VFP.Servername. This guy has a bumch of info about the server.

Also check out SYS(2336)

Regarding SET PROCEDURE TO - if you can you might find it more efficient just to encapsulate your methods inside your server class.

I see you have Rick and Christof on the phone - so you could not be in better hands.