Re: Recordset in Memory
- From: "John Spencer (MVP)" <spencer4@xxxxxxxxxxx>
- Date: Sun, 22 May 2005 12:28:51 -0400
If you are using standard Access MDB then I know of no way to do what you have
asked other than using an array to hold the information or using a temporary
database and tables in that temp db. Both ideas have been suggested to you already.
SO, your statement is apparently correct.
Michael wrote:
>
> So, I gather, there is no way to accomplish what I want. Is that correct?
>
> Michael
>
> "Douglas J. Steele" wrote:
>
> > Consider putting your temporary tables in a temporary database.
> >
> > Tony Toews shows one way of doing this at
> > http://www.granite.ab.ca/access/temptables.htm
> >
> > --
> > Doug Steele, Microsoft Access MVP
> > http://I.Am/DougSteele
> > (no e-mails, please!)
> >
> >
> >
> > "Michael" <Michael@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:C8454DBF-11B1-441B-829B-03C0700E91F7@xxxxxxxxxxxxxxxx
> > > Since I run these procedures on a regular basis, I just have temporary
> > > tables
> > > set up for this purpose and delete all the records each time I need to,
> > > but
> > > the database gets bloated. For example, my .mdb file is usually 11MB, but
> > > after running this process once, it grew to 123MB - eventhough all the
> > > temporary records had been deleted. I have to compact the .mdb each time
> > > to
> > > get it back to it's normal 11MB size.
> > >
> > > I was just wondering if there's a way to populate a recordset in memory,
> > > use
> > > it, and then remove it from memory when done without having to store it to
> > > a
> > > table first. I don't think an array would work because the number of
> > > records
> > > I need for the temporary recordset is different each time.
> > >
> > > Thanks,
> > >
> > > Michael
> > >
> > > "Brian Stoll via AccessMonster.com" wrote:
> > >
> > >> I haven't tried it, but can't you delete a table from code? When you're
> > >> done using it, IE: in the Exit_someThing_someFunction, you could delete
> > >> the
> > >> form you created...
> > >>
> > >> Sorry, I don't know of a way to do it all in memory - unless you save all
> > >> the fields in the recordset as a variable, then you aren't creating a new
> > >> table, just a bunch of variables.
> > >>
> > >> --
> > >> Message posted via http://www.accessmonster.com
> > >>
> >
> >
> >
.
- References:
- Recordset in Memory
- From: Michael
- Re: Recordset in Memory
- From: Brian Stoll via AccessMonster.com
- Re: Recordset in Memory
- From: Michael
- Re: Recordset in Memory
- From: Brian Stoll via AccessMonster.com
- Re: Recordset in Memory
- From: Michael
- Re: Recordset in Memory
- From: Douglas J. Steele
- Re: Recordset in Memory
- From: Michael
- Recordset in Memory
- Prev by Date: Re: Recordset in Memory
- Next by Date: Re: Recording users using a DB
- Previous by thread: Re: Recordset in Memory
- Next by thread: Re: Recordset in Memory
- Index(es):
Relevant Pages
|