You could try... The other option may be to use &#39;+&#39; as an alternative - though that&#39;s primarily for URL space encoding, not sure how LDAP will respond.<br><br><div class="gmail_quote">On 11 November 2010 10:28, Mike Evans <span dir="ltr">&lt;<a href="mailto:mike@tandem.f9.co.uk">mike@tandem.f9.co.uk</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
<br>
On 11/11/10 09:35, Dan Attwood wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
no it doesn&#39;t like that, or &#39;\\20-\\20&#39; that i&#39;ve seen elsewhere in the web<br>
<br>
</blockquote></div>
Dan<br>
<br>
No experience of this, but I did see this:<br>
<br>
  <a href="http://www.openldap.org/lists/openldap-software/200010/msg00596.html" target="_blank">http://www.openldap.org/lists/openldap-software/200010/msg00596.html</a><br>
<br>
Which suggests that M$ clients to LDAP translate spaces to %20.  Is it therefore possible that, if the entry was created with a M$ tool that the database actually has %20 in the stored string rather than a space, and therefore searching on that would work?<div>
<div></div><div class="h5"><br>
<br>
_______________________________________________<br>
Kent mailing list<br>
<a href="mailto:Kent@mailman.lug.org.uk" target="_blank">Kent@mailman.lug.org.uk</a><br>
<a href="https://mailman.lug.org.uk/mailman/listinfo/kent" target="_blank">https://mailman.lug.org.uk/mailman/listinfo/kent</a><br>
</div></div></blockquote></div><br>