Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 300563
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T06:55:32+00:00 2026-05-12T06:55:32+00:00

As title says, this issue happens in MS Access 2003 SP1. Does anyone know

  • 0

As title says, this issue happens in MS Access 2003 SP1. Does anyone know what could be solution for this problem?

Pseudo query
select * from a inner join b on a.id=b.id

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T06:55:32+00:00Added an answer on May 12, 2026 at 6:55 am

    For small data sets, there are any number of approaches using various possible string conversions.

    But if your data sets are of any size at all, this will be very slow because it can’t use the indexes.

    You could possibly optimize by joining case insensitively and then using criteria to test whether the case is the same, e.g.:

      SELECT * 
      FROM a INNER JOIN b ON a.id=b.id
      WHERE Asc(a.id) <> Asc(b.id)
    

    This would at least allow the use of an index join so you wouldn’t be comparing “a” to “b” and “a” to “c” (as would be the case with joining on string functions), but only “a” to “a” and “a” to “A”.

    I would suggest that if your data really needs to distinguish case, then you probably need to store it in a database engine that can distinguish case in joins and then pass your SQL off from Access to that database engine (with a passthrough query, for example).

    EDIT:

    @apenwarr suggests using StrComp() in the JOIN (as did @butterchicken yesterday), and this SQL raises a question for me (I’ve updated her/his SQL to use the same table and fieldnames I use above; it’s essentially the same as @butterchicken’s SQL)

      SELECT * 
      FROM a INNER JOIN b
        ON a.id = b.id 
        AND StrComp(a.id, b.id, 0) = 0
    

    It is a fact that Jet will optimize a JOIN on an index exactly the same way it would optimize the equivalent WHERE clause (i.e., implicit JOIN). Stripped down to just the JOIN (presumably on indexed fields), these two SQL statements will be optimized identically by Jet:

      SELECT * 
      FROM a INNER JOIN a
        ON a.id = b.id 
    
      SELECT * 
      FROM a, b
      WHERE a.id = b.id 
    

    My question is whether or not these three will optimize identically:

      SELECT * 
      FROM a INNER JOIN b
        ON a.id = b.id 
        AND StrComp(a.id, b.id, 0) = 0
    
      SELECT * 
      FROM a INNER JOIN b
        ON a.id = b.id 
      WHERE StrComp(a.id, b.id, 0) = 0
    
      SELECT * 
      FROM a, b
      WHERE a.id = b.id 
        AND StrComp(a.id, b.id, 0) = 0
    

    I’m using SO to avoid work I’m supposed to do for tomorrow, so don’t have time to create a sample database and set up SHOWPLAN to test this, but the OP should definitely give it a try and report back on the results (assuming he/she is definitely intending to do this with Jet).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.