>>I am having an issue updating a SQL Server table with a converted string. I pull records that may have lat/lon in somr, nad others that need to be geocoded. I get the lat/lon from a google map, which gives me 8 decimals. I am attempting to update the SQL record using Sqlexec and update, but the number of decimals is getting truncated. Here is a snippet of what I am doing:
>>lnlat=val(lclat) && might be something like 35.064049
>>SQLEXEC(_screen.dsn,'update dbo.incident set latitude=?lnlat where dbo.incident.case_number=?lccaseno')
>>If I query SQL again, the stored value is 35.064, yet other records may show 5 decimals....
>>
>>
>>Does anyone know what is going on?
>
>Did you try to cast to the correct type in VFP side first and may be in the update string also
>update Incident set lattitude = cast(?lnLat as decimal(12,5))
>
>??
Yes, I tried both float and decimal and ?val(lclat). The cast statement didn't do anything more than the val() function. There must be some function that will allow the extra decimals....