I've seen many post regarding VB & VFP with the infamous "SQL Too Long" error. Yet, none of the post have actually demonstrated the solution. Does anybody actually know how to overcome this problem? One post said to use SYS(3055,<some big number, like 2000) but how does one execute that from VB using ADO?
Jeff.
Tue, 07 Jun 2005 03:19:34 GMT
Anders Altber #2 / 2
VB & VFP - SQL Too Long
Hi Are you talking about the sql command. If so, the solution in VFP is to cut it up into smaller strings of maximun 254 bytes. slq= "SELECt ---- -"+"FROM ....." +"WHERE ... " -Anders
Quote:
> I've seen many post regarding VB & VFP with the infamous "SQL Too > Long" error. Yet, none of the post have actually demonstrated the > solution. Does anybody actually know how to overcome this problem? > One post said to use SYS(3055,<some big number, like 2000) but how > does one execute that from VB using ADO?
VB & VFP - SQL Too Long