>>Another thing to check. If you are running Windows 7, you may have to open VFP as Administrator. Or the program from which you are connecting to SQL Server.
>
>it worked yesterday and I made no changes to my VFP
>the only difference is yesterday I was connected to my work network domain and today I am working from home, but the SQLserve is installed locally on my laptop
>
>the only difference is yesterday I was connected to my work network domain and today I am working from home, but the SQLserve is installed locally on my laptop

Big difference. The trusted Connection that worked yesterday was using your domain credentials. You can act as admin on the server because of your local credentials.

Follow the advice in the link I sent you (the Dmitri whomever answer). It tells you how to enable the sa account (it's disabled by default - hence it doesn't work) and how to set a password on it. Then put the password in the connectionstring using username and password, and use that to connect.

>
>
>
>>
>>>that's the name of my laptop
>>>it worked yesterday
>>>
>>>
>>>>To me the server name seems to be "questionable." In my experience the server name usually something like
>>>>computername\SQL2008 or computername\SQLEXPRESS. Check the name you see in the SSMS.
>>>>
>>>>HTH.
>>>>
>>>>>yesterday I installed SQL2008 developer
>>>>>
>>>>>I could connect with this:
>>>>>

>>>>>
>>>>>strConnectionString	= [Driver={SQL Server};Server=OTT-LT1026;Database=kba_sql;Uid=sa;pwd=]
>>>>>strConnectionString	= [Driver={SQL Server};Server=OTT-LT1026;Database=kba_sql;Trusted Connection]
>>>>>
>>>>>strSQL				  = [select * from claims where 1=1 ] && or what ever sql statement you are passing.
>>>>>csrCursorToBeReturned = [csrNames]
>>>>>
>>>>>intHandle = SQLSTRINGCONNECT(strConnectionString)
>>>>>
>>>>>intResults = SQLEXEC(intHandle, strSQL, csrCursorToBeReturned)
>>>>>
>>>>>

>>>>>
>>>>>today it times out
>>>>>with SQL management studio I connect just fine
>>>>>
>>>>>what could be wrong?
>>>>>
>>>>>Peter