Thanks for your reply!

I print out the statement in white for debugging purposes.

I ran this query against the DB and it came back fine, but in the script it hangs: 
SELECT bb_id, emp_user_name, bb_activity_code, bb_model, bb_pin, bb_ph
+one, bb_imei_esn_dec, bb_status, bb_region_code FROM blackberry ORDER
+ BY emp_user_name

[download]
This script returned no values in Access, but once i removed the emp_user_name LIKE '%%' part, it ran fine: 
SELECT bb_id, emp_user_name, bb_activity_code, bb_model, bb_pin, bb_ph
+one, bb_imei_esn_dec, bb_status, bb_region_code FROM blackberry WHERE
+ emp_user_name LIKE '%%' AND bb_status='DEPLOYED' ORDER BY emp_user_n
+ame

[download]
I'm going to make a few modifications to see if i can fix it now that i have more to work with.

Thanks for the advice!

In reply to Re^2: Search breaks based on search string by Kiko
in thread Search breaks based on search string by Kiko

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.