I have a database of test cases for my company's Software Certification department. Each test case is a string of 10 numbers where the first 7 numbers identify which application the test case refers to and the last 3 numbers identify the unique test case.<BR><BR>I had set up a search wizard in which users could search for test case IDs using wildcards. If the user did not know a certain number in the ID, they could use a # sign.<BR><BR>This worked for over a year and a half, but yesterday someone called to let me know that it wasn't working anymore. I did some investigating and from what I can tell it looks like the # sign is no longer being accepted as a wildcard character.<BR><BR>The only thing I can think of that has changed is that about a month or so ago I upgraded to MDAC 2.5 from MDAC 2.1.<BR><BR>Here's the real kicker -- I created a simple executable in Visual Basic and my SQL statement works just fine whether I use MDAC 2.1 or 2.5!<BR><BR>Here's my code, in case it will help:<BR><BR>strConnect = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:inetpubwwwrootdocs est_casesdbTestCases.mdb"<BR>strSource = "SELECT sCaseIDPrefix, sCaseID, sTitle, bPass, blnActive FROM tTestCases WHERE sCaseIDPrefix LIKE '#######'"<BR>Set objRs = Server.CreateObject("ADODB.Recordset")<BR>objRs.Op en strSource, strConnect<BR>If Not objRs.BOF And Not objRs.EOF Then<BR> arrData = objRs.GetRows<BR>End If<BR>objRs.Close<BR>Set objRs = Nothing<BR><BR>I suppose another take on this is: is there another wildcard character I could (or should) be using? I know about the % sign, but that takes the place of any number of characters. I just want the wildcard to stand in for one character.<BR><BR>Please ask if there's anything more you need to know in order to answer this.<BR><BR>Thanks!