I personally would recommend staying away from the DECIMAL type, as it Limit if the long datatype, after which your data will be corrupted.ģ) DECIMAL can be passed to different VB6 Datatypesĭepending on how you define the DECIMAL column when creating the table. If a BIGINT is brought into a long, you will be ok up to the You can use the MyODBC option of 16384 (convert BIGINT to INT) to make themįunnel down, but from what I understand your BIGINT is then limited to the size With VB6 is not reccomended, but you may have some luck with the largerĢ) BIGINT cannot be used with ADO, as it will cause errors, Passing to MySQL is rounded off before you post it. VB, so data must be stored in a double, which is actually a floating-pointĭatatype, therefore, be careful to make sure that any value that you will be MySQL Datatypeġ) There is no such thing as a 32 bit unsigned integer in While you will not necesscarily get anĮrror (you get a warning in the mysql client), data corruption will occur. Section), in these situations you need to take care that the VB6 value is not Hold a larger value than the MySQL equivalent (marked with a * in the notes Below is a table of the different MySQL and The variant should be avoided whenever possible, as it can be veryĬPU and memory intensive. Not specify a datatype when you declare a variable, which defaults the datatype Worrying about which type of data is coming from your database, you can simply Visual Basic can be very loose with it's data types.
0 kommentar(er)
