ADO : can't find a user, but the user exists !
in [VbScript]
|
From: Francois Lafont on 10 Sep 2010 18:26 Le 10/09/2010 23:26, James Whitlow wrote : > Try adding the line: > > objCommand.Properties("Page Size") = 999 > > ...right after the 'objCommand.ActiveConnection = objConnection' line: Great ! It works. Thanks a lot. :-) But, I have 2 questions : 1) Is it possible to have some explanations of the "Page Size" property ? I have not understood the little pieces that I have found on the Web. For example, if I replace "999" by "1", the script works too. Why ? 2) With your line (objCommand.Properties("Page Size") = 999), do I have the absolute guarantee on the fact that the .find method will tell me systematically the truth ? -- Fran�ois Lafont
From: James Whitlow on 10 Sep 2010 21:34 "Francois Lafont" <francois(a)nospam.invalid> wrote in message news:eEIUBdTULHA.4344(a)TK2MSFTNGP02.phx.gbl... > Le 10/09/2010 23:26, James Whitlow wrote : > >> Try adding the line: >> >> objCommand.Properties("Page Size") = 999 >> >> ...right after the 'objCommand.ActiveConnection = objConnection' line: > > > Great ! It works. Thanks a lot. :-) > > But, I have 2 questions : > > 1) Is it possible to have some explanations of the "Page Size" property > ? I have not understood the little pieces that I have found on the Web. > For example, if I replace "999" by "1", the script works too. Why ? > > 2) With your line (objCommand.Properties("Page Size") = 999), do I have > the absolute guarantee on the fact that the .find method will tell me > systematically the truth ? 1) Hopefully Richard Mueller will chime in. He has a lot better understanding on this subject that I do. It has been my experience that if you don't set the page size (leave it at the default) or set it to a value at or above the default record size that AD is configured to (normally 1000), it will return a recordset of that size. If you set it to anything below the default, it will return all records. 2) I never like to deal in absolutes (been burned too many times), but I think it very likely that it will always work as expected.
From: Al Dunbar on 12 Sep 2010 12:23 "James Whitlow" <jwhitlow.60372693(a)bloglines.com> wrote in message news:#4m44FVULHA.4880(a)TK2MSFTNGP06.phx.gbl... > "Francois Lafont" <francois(a)nospam.invalid> wrote in message > news:eEIUBdTULHA.4344(a)TK2MSFTNGP02.phx.gbl... >> Le 10/09/2010 23:26, James Whitlow wrote : >> >>> Try adding the line: >>> >>> objCommand.Properties("Page Size") = 999 >>> >>> ...right after the 'objCommand.ActiveConnection = objConnection' line: >> >> >> Great ! It works. Thanks a lot. :-) >> >> But, I have 2 questions : >> >> 1) Is it possible to have some explanations of the "Page Size" property >> ? I have not understood the little pieces that I have found on the Web. >> For example, if I replace "999" by "1", the script works too. Why ? >> >> 2) With your line (objCommand.Properties("Page Size") = 999), do I have >> the absolute guarantee on the fact that the .find method will tell me >> systematically the truth ? > > 1) Hopefully Richard Mueller will chime in. He has a lot better > understanding on this subject that I do. I haven't seen him here for a while, so perhaps he has "left the building" as they say. You might find some useful info on his website at: http://www.rlmueller.net/freecode6.htm /Al > It has been my experience that if you don't set the page size (leave it > at the default) or set it to a value at or above the default record size > that AD is configured to (normally 1000), it will return a recordset of > that size. If you set it to anything below the default, it will return all > records. > > 2) I never like to deal in absolutes (been burned too many times), but I > think it very likely that it will always work as expected. > >
First
|
Prev
|
Pages: 1 2 Prev: match computers in 2 text files Next: Move printers from win2003 cluster to win2008 cluster |