>>>I'm trying to connect to an ODBC datasource using the SqlStringConnect function, but i'm getting a 1903 error, 'String is too long to fit'.
>>>
>>>The connection string is greater than 255 characters, and i have no way of reducing its length. It contains a series of file names including paths and an unlock key which is 128 characters long.
>>>
>>>Any ideas how i can still use this function, so i can save myself from having to use oledb, which doesn't appear to have the 255 character restriction on a connection string.
>>
>>I post this BUG to VFPT on Thread #1057411.
>>
>>VFP checks the length of the string, and if it overcomes the 254 characters it refuses the command.
>>There is no solution now.
>>
>>Don't have the opportunity of sending the paths and an unlock key with a SQLEXEC ?
>
>You're right. I would never thought of it. Then he can first make a simple connection and do rest with sp_attach etc or use a filedsn.
>Cetin

The problem is that the backend can not to be SQL Server,
and a filedsn solution is not a intrinsically sure solution
(I think that the process it needs to lose the control of the file for some microsecond)

The VFPT has to remove this control of length.