Problem #2 Unreliable querys when linking to SQL Server 2005

Office 2003 SP3

This one is much harder. It seems when you like Access tables to SQL Server
tables, and one or more of the joins are via GUIDs or in Access Point of View
ReplicationIDs and you have WHERE clauses on either type of tables, you get
no results back.

This doesn't happen all the time, and usually I have to create a view in Sql
Server and do the WHERE on that and it's ok again.

I thought this was going to be fixed in Windows XP SP3 and\or Office 2003
SP3 but there are still problems.

In a 1-m join, there are sometimes issues when the criteria applies to
fields in the many-side table. You may have to nest the queries. Create
qry1 of just the many-side table and apply the criteria. Then join the
1-side table to qry1 without criteria.
"Cheval" wrote in message
...
Office 2003 SP3

This one is much harder. It seems when you like Access tables to SQL
Server
tables, and one or more of the joins are via GUIDs or in Access Point of
View
ReplicationIDs and you have WHERE clauses on either type of tables, you
get
no results back.

This doesn't happen all the time, and usually I have to create a view in
Sql
Server and do the WHERE on that and it's ok again.

I thought this was going to be fixed in Windows XP SP3 and\or Office 2003
SP3 but there are still problems.

Hi Pat,

Slower and more painful, but ok thanks for that. I'm curious why it only
happens when performing joins over GUIDs and ReplicationID fields?

"Pat Hartman" wrote:

In a 1-m join, there are sometimes issues when the criteria applies to
fields in the many-side table. You may have to nest the queries. Create
qry1 of just the many-side table and apply the criteria. Then join the
1-side table to qry1 without criteria.
"Cheval" wrote in message
...
Office 2003 SP3

This one is much harder. It seems when you like Access tables to SQL
Server
tables, and one or more of the joins are via GUIDs or in Access Point of
View
ReplicationIDs and you have WHERE clauses on either type of tables, you
get
no results back.

This doesn't happen all the time, and usually I have to create a view in
Sql
Server and do the WHERE on that and it's ok again.

I thought this was going to be fixed in Windows XP SP3 and\or Office 2003
SP3 but there are still problems.

I am not sure that it is specifically a GUID issue. It is more likely the
internal order of operations that causes the problem.
"Cheval" wrote in message
...
Hi Pat,

Slower and more painful, but ok thanks for that. I'm curious why it only
happens when performing joins over GUIDs and ReplicationID fields?

"Pat Hartman" wrote:

In a 1-m join, there are sometimes issues when the criteria applies to
fields in the many-side table. You may have to nest the queries. Create
qry1 of just the many-side table and apply the criteria. Then join the
1-side table to qry1 without criteria.
"Cheval" wrote in message
...
Office 2003 SP3

This one is much harder. It seems when you like Access tables to SQL
Server
tables, and one or more of the joins are via GUIDs or in Access Point
of
View
ReplicationIDs and you have WHERE clauses on either type of tables, you
get
no results back.

This doesn't happen all the time, and usually I have to create a view
in
Sql
Server and do the WHERE on that and it's ok again.

I thought this was going to be fixed in Windows XP SP3 and\or Office
2003
SP3 but there are still problems.

Hi Pat,

ok for you, but for our setup it only reproduces itself when joining between
Sql Server GUID and Access ReplicationID fields.

"Pat Hartman" wrote:

I am not sure that it is specifically a GUID issue. It is more likely the
internal order of operations that causes the problem.
"Cheval" wrote in message
...
Hi Pat,

Slower and more painful, but ok thanks for that. I'm curious why it only
happens when performing joins over GUIDs and ReplicationID fields?

"Pat Hartman" wrote:

In a 1-m join, there are sometimes issues when the criteria applies to
fields in the many-side table. You may have to nest the queries. Create
qry1 of just the many-side table and apply the criteria. Then join the
1-side table to qry1 without criteria.
"Cheval" wrote in message
...
Office 2003 SP3

This one is much harder. It seems when you like Access tables to SQL
Server
tables, and one or more of the joins are via GUIDs or in Access Point
of
View
ReplicationIDs and you have WHERE clauses on either type of tables, you
get
no results back.

This doesn't happen all the time, and usually I have to create a view
in
Sql
Server and do the WHERE on that and it's ok again.

I thought this was going to be fixed in Windows XP SP3 and\or Office
2003
SP3 but there are still problems.