RE: Two PCs Different Results



Our IT department controls all the regional setting through out Blue Cross FL.
The code in the query that returns the "DueDate" give me the correct answer
but the order changes on any other PC?

I'm trying everything I can think of, sorting, creating new queries, doing
the same on other PC's.. No matter what I do the order only works on this
PC...

That makes no sense.........



"Klatuu" wrote:

Dan,

I don't know the answer for sure, but here is something you can check, if
you have not already.

Be sure the regional settings on both computers are the same.

--
Dave Hargis, Microsoft Access MVP


"Dan @BCBS" wrote:

Sort changes between PC's!!
With Access 2000 and tables linked to SQL db tables.
I get different results on any other PC and it makes no sense.

This is a very simple query. (Read notes below)

SELECT tblTrackingData.TR_GRIEVANCECOORDINATOR, tblTrackingData.TR_CLOSEDATE
FROM (tblTrackingData LEFT JOIN tblStatus ON tblTrackingData.TR_STATUS =
tblStatus.S_Status) LEFT JOIN tblUsers ON
tblTrackingData.TR_GRIEVANCECOORDINATOR = tblUsers.RACFID
GROUP BY tblTrackingData.TR_GRIEVANCECOORDINATOR, tblTrackingData.TR_CLOSEDATE
HAVING (((tblTrackingData.TR_CLOSEDATE) Is Null));

Then the following code added gives me a due date. I get the correct
information on my PC. When I run this same query on another PC the Due Date
order changes.
Does not matter if I sort by due date, I have also created a new query from
this query and sorted by Due Date - when I go to any other PC the Due Date
order changes. This is messing me up because I need to identify the nearest
date in a report.

DueDate: IIf([tr_inquirytype] In
("IN","NC"),Null,IIf([TR_DATE_TIMERCVD_HOI]<#07/01/2002#,"N/A",IIf([tr_24expedited]=True,DateAdd("h",24,[TR_DATE_TIMERCVD_HOI]),IIf([tr_expedited]=True,DateAdd("h",72,[TR_DATE_TIMERCVD_HOI]),IIf([tr_product]
In ("HO") And [tr_CaseType] In
("C","G"),[TR_DATE_TIMERCVD_HOI]+30,IIf([tr_product] In ("HO") And
[tr_CaseType]="P",[TR_DATE_TIMERCVD_HOI]+15,IIf([tr_product] In ("HO") And
[tr_InquiryType]="AD",[TR_DATE_TIMERCVD_HOI]+15,IIf([tr_product] In
("MM","MD","MP","AY") And [tr_InquiryType]="GR" Or
[tr_CaseType]="G",[TR_DATE_TIMERCVD_HOI]+30,IIf([tr_inquirytype]="OD",[tr_date_timercvd_hoi]+30,IIf([tr_inquirytype]="RD",[tr_date_timercvd_hoi]+7,IIf([tr_product]
In ("MM","MD","MP","AY") And
[tr_CaseType]="C",[TR_DATE_TIMERCVD_HOI]+60,IIf([tr_product] In
("MM","MD","MP","AY") And
[tr_CaseType]="P",[TR_DATE_TIMERCVD_HOI]+30))))))))))+IIf([tr_casetype] In
("C","P","G") And [tr_product] In ("MM","MD","MP","AY") And
[tr_extension]=True,14,0)))

PLEASE HELP
.



Relevant Pages

  • RE: Two PCs Different Results
    ... Dave Hargis, Microsoft Access MVP ... but the order changes on any other PC? ... This is a very simple query. ... FROM (tblTrackingData LEFT JOIN tblStatus ON tblTrackingData.TR_STATUS = ...
    (microsoft.public.access.queries)
  • RE: Two PCs Different Results
    ... It is sounding like a format issue. ... Are you suggesting that a text box in my report have a control source ... but the order changes on any other PC? ... This is a very simple query. ...
    (microsoft.public.access.queries)
  • RE: Two PCs Different Results
    ... I was only going to put it into a text box source code on the report. ... Dave Hargis, Microsoft Access MVP ... The code in the query that returns the "DueDate" give me the correct answer ... but the order changes on any other PC? ...
    (microsoft.public.access.queries)
  • RE: Two PCs Different Results
    ... I'll try creating a new query from the orginal the adding your suggestion to ... Dave Hargis, Microsoft Access MVP ... but the order changes on any other PC? ...
    (microsoft.public.access.queries)
  • Re: SQL Server 2005: Cannot convert {fn CURDATE()} to "datetime" datatype
    ... Yes, I agree that the Date converting is not rely on the regional setting, ... I mentioned it because those query tools such as the Query Analyzer or ... me a test database which will result the error when performing query (use ...
    (microsoft.public.sqlserver.odbc)

Loading