>Hi,
>
>I have a vfp com object (accessed from an asp page) that I am changing from vfp 7 to vfp 9 (to add new features).
>
>In numerous places I take a cursor and convert it to a recordset and then return the recordset. Like the following:
>

>	SELECT * FROM student WHERE istudentid=813 INTO CURSOR _S
>	Local oRecordset, oVFP
>
>	oRecordset = Createobject("ADODB.RecordSet")
>	oVFP = Createobject("vfpcom.comutil")
>	oVFP.CursorToRS(oRecordset, "_S")
>	Release oVFP
>	Close Databases All
>
>	Return oRecordset
>

>When the COM object is compiled in vfp 7 it works. When it is compiled in vfp9 it doesn't; the asp page will just hang and the line in the vfp com object that it gets stuck on is
>

>   oVFP = Createobject("vfpcom.comutil")
>

>The function works when compiled into vfp 7 and when I run it from the command window in vfp9, but when an asp page is accessing it, it just hangs.
>
>I have downloaded and installed the newest version of vfpcom.dll from microsoft (says for vfp 8).
>
>
>Is the vfpcom not supported in vfp9?
>Is it because I have windows service pack 2?
>
>Any assistance would be appreciated.
>
>Thanks,
>Malonep
>
>(not sure if I put it in the correct category - the first time)

I didn't see VFP9 yet. What comes to mind is that you might have a problem with security.

Also I didn't use VFPCom since 6, why do you need it? You could directly do that select with an ADO connection or as it's listed in its feature list VFP9 stored procs can return cursors. You might even directly use VFPOLEDB or ODBC from within asp or even htm.

Or return data as XML.
Cetin