Error 3035 is "System Resource Exceeded"
I'm throwing this error in a procedure that creates a pass through
query. The procedure has worked tried and true for many years, first in
A97 and now in A2003, but for this particular use of it, I'm throwing
the above described error.
The variable declarations are thus:
Sub sCreatePT(strSql As String, strQryName As String)
In the case in question, strSql is a largish Oracle SQL statement that
is 80,362 characters long.
Help says a fixed length string is limited to 64K, but I had always
assumed I was working with variable length strings?

Signature
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto
Tom van Stiphout - 13 Mar 2006 15:10 GMT
On what line?
This test program works fine on my Access 2003:
Sub TestString()
Dim s As String
s = String$(90000, 65)
Debug.Print Len(s)
sCreatePT s, "test"
End Sub
Sub sCreatePT(strSql As String, strQryName As String)
Debug.Print Len(strSql)
End Sub
-Tom.
>Error 3035 is "System Resource Exceeded"
>
[quoted text clipped - 12 lines]
>Help says a fixed length string is limited to 64K, but I had always
>assumed I was working with variable length strings?
salad - 13 Mar 2006 18:21 GMT
> Error 3035 is "System Resource Exceeded"
>
[quoted text clipped - 12 lines]
> Help says a fixed length string is limited to 64K, but I had always
> assumed I was working with variable length strings?
If I create a query in the query builder, I might see something like
Select Table.ID, Table2.Name, Table.Address...
This is a stab in the dark...
Since your sub is passed a string and perhaps running a SQL statement,
can you chop off the table names where possible. You will have to
specify the table names where the field name exists in more than 1
table, but for those where the field names exist in only 1 table, remove
the qualifiers.
IOW, the code could look like
Select ID, Name, Address...
That might get it under any limitation you currently have on strings.
Just a stab...