E
eddsa21
Hello,
Long time Access user (2.0, 97 and 2002/XP). I am using
Access 2000 at work (new to that particular version), and
I found something very unusual that I haven't seen before.
I have a query I'm trying to run but it just will NOT
execute. No error messages, no results, no nothing, it
just goes to hourglass and back to arrow cursor within
Design View after about 3 seconds.
There is one field I have from one of the joined tables i
the query. If I take it out the query runs, but if I put
it in, it won't. There is an identical field from another
joined table, if I use that the query works. (I tried with
both in and with only the one from the bad table in by
itself to no avail.)
The data is from SQL Server 2000 via ODBCly-linked tables.
Could this be an ODBC issue? I've already found a couple
of those (left joins won't work. The patch for it won't
make it work either). The joins in this query are all
inner joins, however one of the tables in the query is
actually a query that uses a subquery to pull the data in
the field in question. Could the aggregate of all these
factors be akin an outer join and causing ODBC and the Jet
engine to belch?
Any thoughts would be appreciated.
Regards,
eddsa21
Long time Access user (2.0, 97 and 2002/XP). I am using
Access 2000 at work (new to that particular version), and
I found something very unusual that I haven't seen before.
I have a query I'm trying to run but it just will NOT
execute. No error messages, no results, no nothing, it
just goes to hourglass and back to arrow cursor within
Design View after about 3 seconds.
There is one field I have from one of the joined tables i
the query. If I take it out the query runs, but if I put
it in, it won't. There is an identical field from another
joined table, if I use that the query works. (I tried with
both in and with only the one from the bad table in by
itself to no avail.)
The data is from SQL Server 2000 via ODBCly-linked tables.
Could this be an ODBC issue? I've already found a couple
of those (left joins won't work. The patch for it won't
make it work either). The joins in this query are all
inner joins, however one of the tables in the query is
actually a query that uses a subquery to pull the data in
the field in question. Could the aggregate of all these
factors be akin an outer join and causing ODBC and the Jet
engine to belch?
Any thoughts would be appreciated.
Regards,
eddsa21