I've got a sql server view that returns data, as a linked table to
access97 (qryPlannedPurPT)
this link table is used in an access query (qryPlannedPUR) that uses
all of the linked table fields and adds a couple of calculated fields
when I create a second query using qryPlannedPUR that adds a specific
WHERE clause
I may or may not get the correct resultset
I always get the correct number of rows, but one of the row contains
the wrong data
if I take the sql server view, which is just a query, and I create an
ms-access passthrough query and call it qryPlannedPurPT, my second
query above, always (10 out 10) returns the correct resultset
so then I went back to my linked table called qryPlannedPurPT and I
change my second query above to use it instead of qryPlannedPUR, I get
the correct resultset
so it looks like access97 sometimes has a problem using qryPlannedPUR
which is based on a link table (sql server view) qryPlannedPurPT
but it has no problems if the link-table references a sql-server
table....
has anyone seen this type of problem ?
I'm going to use the ms-access passthrough query for now, both I have
other linked-tables that reference sql server views... and it now
scares me that the result sets for those may not always be correct
