"p byers" <firstname.lastname@example.org> wrote in message
> Jeff C wrote:
>> Jeff C
>> Live Well .. Be Happy In All You Do
>> "p byers" wrote:
>> > Hi folks
>> > I need a function that needs to iterate many (up around 20) times.
>> > It needs to Select records from a table
>> > BUT if I do it as a single nested ude function, the Record Set from
>> > previous iterations will be lost.
>> > The only way that I can see of doing it is to have twenty functions
>> > each
>> > with a slightly different FunctionName and RecordSetName !!
>> > Any ideas for simple was to do it with just one function and one
>> > TableOpen ??
>> Have you considered creating action queries and/or VBA code that
>> accomplishes your process and then placing your process into a macro
>> can repeat).
>> Then you can use Access command line functionality to run the macro from
>> batch file which could then be scheduled?
>> Sample command line:
>> "full path to access.exe" "full path to atree.mdb" /x "name of macro"
>> > Thanks in anticipation
>> > Pete (Northolt UK)
> Thank you for the suggestion - I will give it a try.
> Since the original post, I have been mulling it over and am wondering
> adding a "Sequence number" on the table
> Populating it as phase One of a process
> Re-Read the table "ORDER BY" the sequence number
> But as the purpose of the script is to examine the Table (which contains
> describing a tree) for closed loops,
> The creating of such sequence numbers might get into an everlasting
> loop !!
> Actually, that may have given me the answer
> Set the sequence number to null to start with
> If I find the Sequence number is present already before I put one in -
> indicates a loop !!
> Sorry to have asked a question and then rambled on in this post - I have
> contemplating the problem for several days before the original post
> Pete (Northolt UK)
I don't understand what you are trying to do, but from your last response I
wonder if a dictionary object would help. This is great for keeping track of
unique items. I use it when working with nested groups, for example, to
prevent an infinite loop, or anytime I use recursive functions. If all you
want is to count for 20 iterations (or nested loops), then a counter may be
Also, it looks to like your 20 Connection objects are identical. If so,
there is no reason why you cannot use one. In the past I have used several
nested Recordset objects but one Connection object with success. However, I
would recommend closing each Recordset object when you are done with it, and
then closing the Connection object when you are done with that.
MVP Directory Services
Hilltop Lab - http://www.rlmueller.net