A2k Case Sensitivity

[hhutchinson]

I am running A97 and A2k on the same NT machine. I have a database that has upper and lower case values in the same field (eg &quot;d&quot; and &quot;D&quot. I know having upper and lower values is the same field is not a good idea - but I inherited this system <br>
<br>
In Access97 I can run a select query and the system will differentiate betweeen the &quot;d&quot; and the &quot;D&quot;. Placing &quot;d&quot; on the criteria line only brings back the &quot;d&quot; rows.<br>
<br>
In A2k I am using the same database and the same query, but Access will not differentiate between &quot;d&quot; and &quot;D&quot;. So if I put &quot;d&quot; on the critieria line I get the &quot;D&quot; and the &quot;d&quot; rows.<br>
<br>
This presents a problem because in this database and others I've worked with - the upper and lower case values mean different things.<br>
<br>
I've checked the option settings and any other settings I can think of and they are the same in both systems. Other users of A2k have told me they can replicate this problem. There is no info I've found in Access help, or on Microsoft's website, and Dell (where I bought the software preloaded) is clueless.<br>
<br>
Any help/comments would be appreciated! Thanks.

 

[DougP]

Well as you know from Computer 101 the letter &quot;d&quot; in lower case is ASCII number 100 and &quot;D&quot; is ASCII 68<br>
to find any ASCII number use this function.<br>
Num = ASC(MyValue)<br>
This may help in your quest.<br>
<br>
Here ia groovey function I whipped up.<br>
<br>
expr1: ConverToASCII([fieldname]) &lt;&lt;&lt;put this in your query<br>
<br>
Put the following code in a module<br>
<br>
Public Function ConverToASCII(MyValue As String)<br>
ConverToASCII = Asc(MyValue)<br>
End Function<br>
<p> DougP<br><a href=mailto: dposton@universal1.com> dposton@universal1.com</a><br><a href= > </a><br>

 

[rhicks]

This is out of Access Help:<br>
(Search Help for Option Compare Statement)<br>
<br>
The Option Compare statement specifies the string comparison method (Binary, Text, or Database) for a module. If a module doesn't include an Option Compare statement, the default text comparison method is Binary.<br>
<br>
Option Compare Binary results in string comparisons based on a sort order derived from the internal binary representations of the characters. In Microsoft Windows, sort order is determined by the code page. A typical binary sort order is shown in the following example:<br>
<br>
A &lt; B &lt; E &lt; Z &lt; a &lt; b &lt; e &lt; z &lt; À &lt; Ê &lt; Ø &lt; à &lt; ê &lt; ø<br>
<br>
HTH<br>
RDH <p>Ricky Hicks<br><a href=mailto: rdhicks@mindspring.com> rdhicks@mindspring.com</a><br><a href= > </a><br>