This past week I was implementing an "evolving" solution for a client that uses BDC and SPQuery and ran into some difficulty using SPQuery against a document library containing folders. Imo linea: assign "recursive" Ad secundum proprium quaestionis.

Missionem meam:

• Die Lune, Ego upload a tabellae et conpleamus aliqua notitia meta.
• Sequenti septimana, I upload a new document. Much of this new document’s meta data is based on the document I uploaded on Monday (which we call the "master document").
• Diximus creavit textus muneris ut suggero a latitudo autem ante faciem BDC-familiaris interface ut album ut users ut facile locus Lune per tabellae quaestionis titulus.
• A BDC data column provides a friendly user interface. (Hæc est pars agminis conatu ad usura BDC pro amiciores Lookup).

Latitudo autem ante faciem ultima BDC cultum adhibet query hoc facere lookup:

 // U2U tool usus ad assistunt in generatione hac quaestione CAML.
      oQuery.Query =
        "<Ubi>";

      si (titleFilter.Length > 0)
        oQuery.Query   =
          "  <Et>";

      oQuery.Query   =
        "    <Et>" +
        "      <Geq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + MinID + "</Valor>" +
        "      </Geq>" +
        "      <Leq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + maxId + "</Valor>" +
        "      </Leq>" +
        "    </Et>";

      si (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Continet>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Valor>" +
          "    </Continet>" +
          "  </Et>";
      oQuery.Query   =
        "</Ubi>";

In initialis stadio progressionem, this worked great. Autem, nos in introductus folders album solvere quaestiones et subito quidam, my BDC picker wouldn’t return any results. I tracked this down to the fact that the SPQuery would never return any results. We used folders primarily to allow multiple files with the same name to be uploaded but with different meta data. When the file is uploaded, partum a folder item ex album, et tunc permoveo lima ibi ID scriptor (Ego scripsit quod hic; weve 'had mixta results sed cum omnis aditus, illud bene operetur). The user don’t care about folders and in fact, don’t really understand that there are any folders. We have configured all the views on the library to show items without regard to folders.

I hit this problem twice as the technical implementation evolved and solved it differently each time. The first time, I wasn’t using the CONTAINS operator in the query. Without a CONTAINS operator, I was able to solve the problem by specifying the view on the SPQuery’s contructor. Instead of using the default constructor:

SPList oList = web.Lists["Documents"];

SPQuery oQuery = novum SPQuery();

Ego potius uteretur sententia machinator quod specificatur:

SPList oList = web.Lists["Documents"];

SPQuery oQuery = novum SPQuery(oList.Views["All Documents"]);

Ut problema solvendum et coepi praecessi adepto meus.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, ut mihi indicet, Sic uti non sit simplicior quam GEQ / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", ut in:

oQuery.ViewAttributes = "Scope=\"Recursive\"";

That solved the problem for CONTAINS. In facto, hoc problema solvitur etiam pristinae quaerere et si fecissem peregit recursive primum attributum,, Nec vero causae occurrunt.

Quod visus operetur in aliqua dicentur SPQuery operators (GEQ/LEQ) et non alios, (Continet), copulata hoc, quod non videtur ad operari cum KPIs folder-document continens bibliothecis ducit me ad credendum quod aliqua SPQuery orthogonality exitibus.

Praecipua gratias,:

• At bonum folks U2U et machinatio eorum query.
• Magna est scriptor Michael Hoffer "discendi facere," blog nuntius, comments et responsa.

</finem>

Scribet ad mea blog!