How do I set a text field in a table to be case sensitive?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: kml665 (kml665_at_discussions.microsoft.com)
Date: 12/07/04


Date: Mon, 6 Dec 2004 21:15:02 -0800

I have import a table using ODBC and there is a field that is two alpha
characters which represents a name. These two character fields could be "AB"
or "Ab" or "aB" or "ab" and all four are unique for four different names. I
am trying to run a query which uses the two character field, yet it is
returning multiply names which may have the same characters but disregards
the case of the characters. Any thoughts on either settiing the field in the
table to be case sensitivity or should I focus on the query?



Relevant Pages

  • Re: Truncated Memo field displayed on form
    ... 255 characters in any column that is in the combo box's RowSource query. ... My fields down to "Knowledge and Understandings" are fine. ... occurs with the "descriptor" field being truncated on my form. ...
    (microsoft.public.access.forms)
  • Re: DEFCON 16 and Hacking OpenVMS
    ... To reproduce this, apparently one is to enter exactly 511 characters ... Of course it could even be Alpha chip type ... Sampsa's report of VMS vulnerabilities in the Defcon 16 slides. ...
    (comp.os.vms)
  • Re: Using part of a field
    ... See the article "Finding and replacing characters using wildcards" at: ... AS400 SQL may have a different way of doing ... called i.dsn, containing the followiing text: ... sort of thing in a query. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Export to Ascii
    ... characters in a calculated field when you export a query. ... Modify your query to append its output to the temporary table; ... "John Nurick" wrote: ... that instead of concatenating with a delimiter it concatenates a fixed ...
    (microsoft.public.access.externaldata)
  • Re: SQL too long?
    ... I haven't done a thorough analysis here, but I suspect that the number of characters needed to express the SQL may not be as important as the number of aggregate functions like Sumand Countthat you invoke along the way. ... Although what you now have may be correct, assuming no simian behavior on the part of Access, splitting up the Query may also make it easier to debug if you later encounter any questions concerning its correctness, or if you need to revise it in some way. ... For example, in my copy of Access 2000, it says that the "Number of characters in an SQL statement" has a maximum value of "approximately 64,000", so you probably have some wiggle room there, even without using abbreviated aliases for some of the names. ... tblARTrn01.invno) INNER JOIN tblARMst01 ON tblDUPSFreight.invno = tblARMst01. ...
    (microsoft.public.access.queries)