In DELPHI, use adoquery execute an insert statement, in a 64 - bit system computer implementation is not an error, a 32-bit system execution "will be truncated string or binary data", in a 32-bit system, the executed statement in the post to the query analyzer also won't complain, don't know is what reason, each prawn, who met, teach teach, thank you!!!!!

CodePudding user response:

With delphi7

CodePudding user response:

If I remember right,
This error message is "are you going to deposit the string content, its length more than the database of the definition of the field length" meaning;
Personally think that has nothing to do with 32-bit/64,
Solution is, for the string to be deposited in the database, write a function that will be part of super-long removed, then written to the database,

As for is not an error to query analyzer,
Perhaps this check is in ADO!!!!

CodePudding user response:

Should not be the problem of string
32 bit smaller than 64, how long?

CodePudding user response:

Just don't understand, I think it's not super length problem, on a 64 - bit system execution without any problems, only to the 32-bit system execution error

CodePudding user response:

Not met, cut a EXCEPTION look on the graph, and DEBUG the ADO. SQL. The TEXT

CodePudding user response:

on a 32-bit system, suggest this

CodePudding user response:

Field length of what, is absolutely no problem, insert table structure and I built table field properties are the same

CodePudding user response:

Can only see the SQL statement and values, each field

CodePudding user response:

Showmessage (SQL text), copies dialog within the SQL statement to query analyzer to perform inside, look to whether an error?

CodePudding user response:

I had encountered before, should be a string over the length of the SQL database definition,

You can debug showmessage string length,

Should system version should has nothing to do,

CodePudding user response:

This problem is common, should be the string length more than the length of the SQL database tables defined, look to understand,

CodePudding user response:

Is the length of the field, or the field type, this problem is too common, show too not to know

CodePudding user response:

Characters in length and type, string or widestring

CodePudding user response:

You can also use essentially event monitoring to look at his actual to execute SQL statements and your default what is the difference between

Most likely is a field you fill in the content of the super long

CodePudding user response:

Change the database characters in length

CodePudding user response:

So many post, you should attach the field type,
What is wrong input string, such, can help you to analysis,