Well, I get the same results as you! I'm thinking that maybe the use of SPT functions isn't allowed. I'm no expert on the inner workings of VFP but it may be that SPT is VFP-centric and therefore doesn't work outside of the VFP environment. If you really want to use VFP to create your DLLs, try using ADO instead of SPT.
Sorry I couldn't be more help!
>>IIS and ASP use connection pooling for database connections in order to conserve resources. We're not getting anywhere with this, are we! Can you email me the source code for your DLL, or, if it's short enough, post it here? Maybe if I look at it I can figure something out.
>>
>SOURCE CODE
>DEFINE CLASS SubMain AS Custom OLEPUBLIC
> PROCEDURE TransferToSQL
>gnCH=SQLSTRINGCONNECT('DSN=MyDSN;UID=MyUser;PWD=MyPassWord;DATABASE=DatabaseDB')
> IF gnCH < 0
> lcMessage = MESSAGE()
> RETURN lcMessage
> ELSE
> ...
> ENDIF
> ENDPROC
>ENDDEFINE
>
>Thanks
>Nick,
>
>
>>>SQL Server use Standard security.
>>>Also, other ASP pages create a ADO connection to SQL with no problem.
>>>
>>>What is the pooling connection in the error message?
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
