Angus, Thanks for the response.
Yes I'm using the stored proc component. No data aware controls. So, you solution would be something like creating a string: exec sp_InsertVehicleData;1 '2009/01/17 15:48:12',1,'0358104000636686','00000F611B8C',17,$53.5161,$-2.2367,0,$15475. 5996,$0.0000,$0.0000,0,0,'S',0,0,0,0,0,0,0,0,'',$-2.2367,$53.5161,$65535.000 0,0x010358104000636686FF447800344015FF2A00000F611B8C11EAC5738C79105642C0260F C00008B90400000000C0260FC07910564200FF7F47900105,60,1,'447800344015' which is the command captured with the profiler. Am I understanding you correctly? Regards, Andy Angus Robertson - Magenta Systems Ltd wrote: >> I am using an ADO stored proc to call a stored proc on a MSSQL >> server. >> One of the parameters in the stored proc on the server is a >> Decimal(28,20) but delphi detects this in the parameters list and >> sets it to ftBCD, precision 28, scale of 20. > > It sounds like you are using the stored procedure component, and some > data conversion is going wrong. Unless you are using data aware controls > or something, you can build the command and parameter list for the stored > procedure as a simple widestring and use the EXECUTE method in the > connection to run it. You can get a result set and read it as string > numerics, to get whatever precision you need. > > ADO only deals in ASCII, not numerics, all conversions to internal SQL > data types take place in ADO or SQL itself, not Delphi. > > Angus > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be