Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / February 2008

Tip: Looking for answers? Try searching our database.

Problem #2 Unreliable querys when linking to SQL Server 2005

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Cheval - 08 Feb 2008 06:55 GMT
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.
Pat Hartman - 11 Feb 2008 18:39 GMT
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.
> Office 2003 SP3
>
[quoted text clipped - 12 lines]
> I thought this was going to be fixed in Windows XP SP3 and\or Office 2003
> SP3 but there are still problems.
Cheval - 11 Feb 2008 22:56 GMT
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?

> 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
[quoted text clipped - 16 lines]
> > I thought this was going to be fixed in Windows XP SP3 and\or Office 2003
> > SP3 but there are still problems.
Pat Hartman - 14 Feb 2008 14:43 GMT
I am not sure that it is specifically a GUID issue.  It is more likely the
internal order of operations that causes the problem.
> Hi Pat,
>
[quoted text clipped - 24 lines]
>> > 2003
>> > SP3 but there are still problems.
Cheval - 20 Feb 2008 22:43 GMT
Hi Pat,

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

> I am not sure that it is specifically a GUID issue.  It is more likely the
> internal order of operations that causes the problem.
[quoted text clipped - 26 lines]
> >> > 2003
> >> > SP3 but there are still problems.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.