Rx_
Nothing In Moderation
- Local time
- Today, 12:56
- Joined
- Oct 22, 2009
- Messages
- 2,803
Just wanted to know if anyone had heard of this or woul know why it does this.
A SQL View - has Distinct - one of the fields is a large text field.
This works fine. The Access DSN-Less linked table shows all the charaters in the text field.
On the Access side, a query against the the Linked Table had a Select Distinct *
The recordset assigned the result into a string variable.
It should have been over 530 characters - it was one word.
Removing the last two words, it then was about 212 characters (the last half of the complete field).
All the records with about 212 characters (or less) appeared to work fine.
On the Access query, removing the Distinct (just Select *) fixed the problem.
Granted, the 2nd Distinct was not required.
This just seemed like a crazy result. It wasn't as if "oh, the 2nd Distinct is causing this to happen" moment arrived.
Anyone heard of this?
DSN-Less ODBC connections using SQL Server Native Client 11.0 and DAO recordsets.
A SQL View - has Distinct - one of the fields is a large text field.
This works fine. The Access DSN-Less linked table shows all the charaters in the text field.
On the Access side, a query against the the Linked Table had a Select Distinct *
The recordset assigned the result into a string variable.
It should have been over 530 characters - it was one word.
Removing the last two words, it then was about 212 characters (the last half of the complete field).
All the records with about 212 characters (or less) appeared to work fine.
On the Access query, removing the Distinct (just Select *) fixed the problem.
Granted, the 2nd Distinct was not required.
This just seemed like a crazy result. It wasn't as if "oh, the 2nd Distinct is causing this to happen" moment arrived.
Anyone heard of this?
DSN-Less ODBC connections using SQL Server Native Client 11.0 and DAO recordsets.