I've discovered a problem that seems to stem from the Office 2010 version of
MS Query's interaction with the ODBC.
A basic full table grab will not return att rows if certain fields ar
included in the query. Remove those and att rows are returned. I tried
adding a "where is not null" clause an
ARODBC Can return odd things if there is no "WHERE" clause.
Even if the "WHERE" clause returns all entries.
On Aug 2, 8:42 am, Jonas Stumph stevnsvig wrote:
> Hi again, I'll try not to hit ctrl+enter again... sorry for the triple
> posts.
>
> I am still fiddling with this problem, concering ARO
Hi again, I'll try not to hit ctrl+enter again... sorry for the triple
posts.
I am still fiddling with this problem, concering ARODBC and the number
of records to be returned.
I and querying the incident form on a server with 12000 records, and
getting very big variations in how many records a
Hi again.
I am still fiddling with this problem, concering ARODBC and the number
of records to be returned.
I and querying the incident form on a server with 12000 records, and
getting very big variations in how many records are being returned. I
started in excel, and moved to VBscript to 1
Hi again.
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Hey Jonas...
ODBC Connections can sometimes return unusual results. Here are some
quick points that might help:
1) Historically different versions of the ODBC Drivers have had
problems returning data when there are not qualifications (where
clause) even if the qualification returns all records.
Hi listers
I have an interesting problem.
I have been tasked with fetching some data from HPD:Help Desk (ITSM v
7.6.03 both client and ARS server, v 7.6.03)
I ran into an oddity; When Fetching data through ODC (I used Excel to
start with) I only got about 1000 Records. But i expected 12000. I th
7 matches
Mail list logo
