Well, if you use asynch mode, this can cause a lot of problems, such as "Connection Busy" errors when you share connection between views. Anyway, your correction is correct, in help there is the same note ;)
>Vlad:
>Just to follow up for others who might not be aware. I had tried this approach some time ago, but could never get the SQLEXEC to return a result set. I found in BOL where in asynch mode, you have to repeatedly call SQLEXEC until it returns a result set. So I modified your code just a bit as follows:
>
> Local lnRetVal
>
> lnRetVal = SQLEXEC(nHandle, "SELECT @@IDENTITY as nID","MyCursor")
> Do While lnRetVal=0
> lnRetVal = SQLEXEC(nHandle, "SELECT @@IDENTITY as nID","MyCursor")
> EndDo
>
>This seems to always catch it on just the second pass.
>
>Thanks again...
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.