﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <description><![CDATA[Comments for Searching a ClientDataSet]]></description>
    <title><![CDATA[Comments for Searching a ClientDataSet]]></title>
    <link>http://dn.codegear.com/article/29176</link>
    <!-- source: http://dn.codegear.com/article/29176/feed-->
    <dc:date>2008-11-21T13:55:41-08:00</dc:date>
    <item>
      <description><![CDATA[There is an error at the end of the articleWhere it saidThe following figure shows the main form of the CDSSearch project following a call to Locate. Notice that the current record is still the first record in the ClientDataSet, even though the data returned from the call to Locate was found much later in the current index order.Locate must be replace by LookUp.]]></description>
      <title><![CDATA[Error]]></title>
      <managingEditor>
	 (joan llosas)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=35107</guid>
      <dc:date>2003-08-11T22:12:17-07:00</dc:date>
      <pubDate>2003-08-11T22:12:17-07:00</pubDate>
      <source url="http://dn.codegear.com/article/29176/feed">Comments for Searching a ClientDataSet</source>
    </item>
    <item>
      <description><![CDATA[The order  of my query (without index) is:DESCRIPTION-----------------------ACCES P'ADORNACCES P'AJUSTACCES P'ASPIRACCES P'BATHACCES P'COURTACCES P'SOLDACCES PARA PUERTAACCES PLAST...When i do this, i lost the order of the records:  cdsQuery.IndexFieldNames:= DESCRIPTIONThe result is:DESCRIPTION-----------------ACCES P'ADORNACCES P'AJUSTACCES PARA PUERTAACCES P'ASPIRACCES P'BATHACCES P'COURTACCES PLASTACCES P'SOLDCan you help me to resolve this problem ?]]></description>
      <title><![CDATA[Problems with IndexFieldName with string fields !!!]]></title>
      <managingEditor>
	 (Manny Ramirez)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33360</guid>
      <dc:date>2002-10-22T08:53:06-07:00</dc:date>
      <pubDate>2002-10-22T08:53:06-07:00</pubDate>
      <source url="http://dn.codegear.com/article/29176/feed">Comments for Searching a ClientDataSet</source>
    </item>
    <item>
      <description><![CDATA[  Usually, when searching a DataSet, the user prefers that the current record is changed only if a match is found. For that purpose, I found very useful to call the GetBookmark, GotoBookmark, FreeBookmark functions (implemented in TDataSet, an ancestor of TClientDataSet).]]></description>
      <title><![CDATA[Using GetBookmark / GotoBookmark / FreeBookmark]]></title>
      <managingEditor>
	 (Daniel Ardelian)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33306</guid>
      <dc:date>2002-10-12T02:28:37-07:00</dc:date>
      <pubDate>2002-10-12T02:28:37-07:00</pubDate>
      <source url="http://dn.codegear.com/article/29176/feed">Comments for Searching a ClientDataSet</source>
    </item>
    <item>
      <description><![CDATA[Great overview.  I've never used Locate, every day you learn something.How does filter compare as an access mechanism?  It is particularly useful if the results are linked to data aware controls as all the other methods leave the data aware controls pointing to incorrect data if the locate/search etc fails.  What are the performance implications, particularly on large datasets?RegardsRoger Graham]]></description>
      <title><![CDATA[Use of Filter]]></title>
      <managingEditor>
	 (Roger Graham)
</managingEditor>
      <guid isPermaLink="true">http://threads.codegear.com/threads/threads.exe/view?commentid=33289</guid>
      <dc:date>2002-10-10T01:33:56-07:00</dc:date>
      <pubDate>2002-10-10T01:33:56-07:00</pubDate>
      <source url="http://dn.codegear.com/article/29176/feed">Comments for Searching a ClientDataSet</source>
    </item>
    <generator>Atom 1.0 XSLT Transform v1 (http://atom.geekhood.net)</generator>
  </channel>
</rss>