flowpoker.blogg.se

1. ERROR 42000 MICROSOFT ODBC VISUAL FOXPRO DRIVER SYNTAX ERROR HOW TO
2. ERROR 42000 MICROSOFT ODBC VISUAL FOXPRO DRIVER SYNTAX ERROR UPDATE

RE: "SQL: Statement Too Long" Error bborissov (Programmer) 11 Apr 07 14:33ĭeclare Integer DllUnregisterServer In for_vb.Dll Additional comments on this possible solution will be appreciated. So, unless I'm missing something else, I think the solution is for me to find out how I screwed up in a few cases the length of the data stored in the recordset fields before issuing the rs1.Update statement. I think I read in one of the several forums I've visited that the unequal lengths situation can cause the "SQL: Statement Too Long" error (although, as is often the case, the title of the error and related documentation certainly don't reveal that possibility). I've discovered that the length of a FEW of the 87 array data elements used to change recordset fields does not match the length of the corresponding recordset field (in all such cases the data length is less than the field length).

ERROR 42000 MICROSOFT ODBC VISUAL FOXPRO DRIVER SYNTAX ERROR UPDATE

The generated Update statement is less than 1800 characters so it doesn't violate the 8192 limit. However, I think I've found the root cause of the problem and it's NOT the length of the Update statement generated by the VB rs1.Update statement.

ERROR 42000 MICROSOFT ODBC VISUAL FOXPRO DRIVER SYNTAX ERROR HOW TO

My Visual FoxPro site: RE: "SQL: Statement Too Long" Error Sware (Programmer)īeing a VFP and database neophyte I don't understand how to implement the solution offered by Imaginecorp. Doing that would at least tell you whether there was anything wrong with your overall logic, or whether it is indeed some maximum that's being exceeded. Gradually increase that number until the error occurs. My approach would be to try updating a much smaller number of fields. Given that the statement in question is being generated within VB, that's something you would have to ask a VB expert. You asked how to check the length of the Update statement. The fact that you can even access the database suggests that that is not the problem. That said, you're probably right that it won't exceed the 8,192-limit.ĭon't worry too much about the drive issue. You also have to allow for all the separators and other characters that make up the Update statement.

It's not just the number of characters multiplied by the number of fields.