Hi:
I am trying to read a SQL Server text field (Access memo field) using
connection.Open RecordSet("qry with text field") [ODBCDirect]
rather than
database.OpenRe cordSet("qry with text field") [Microsoft Jet]
When I use the connection.Open RecordSet command, my incoming text field
cannot more that 500-odd characters, otherwise the query bombs. This
isn't the case for database.OpenRe cordSet.
Is there something that I can do when I open the connection to make the
SQL Server text fields Access receives in a query longer than 500
fields? Maybe a property on the workspace? The queries with
connections are naturally much faster than with databases.
Peter
I am trying to read a SQL Server text field (Access memo field) using
connection.Open RecordSet("qry with text field") [ODBCDirect]
rather than
database.OpenRe cordSet("qry with text field") [Microsoft Jet]
When I use the connection.Open RecordSet command, my incoming text field
cannot more that 500-odd characters, otherwise the query bombs. This
isn't the case for database.OpenRe cordSet.
Is there something that I can do when I open the connection to make the
SQL Server text fields Access receives in a query longer than 500
fields? Maybe a property on the workspace? The queries with
connections are naturally much faster than with databases.
Peter