Largish system, was 13mb (after de/compile and compact/repair)

It's mostly forms, queries and code. About 40 local tables (with tiny
numbers of records, like 1 to 10)

Recently added a few more TEMP* local tables (no records) and a couple of
screens and a few hundred lines of code

Now it's 44mb after de/compiled and compact/repair!

Another odd thing is a routine that was taking 5 or 6 seconds to run while
building it started completing in 3 seconds. As if the entire routine was
cached.

I don't mind creating a new file and importing everything, but I'd like to
know what caused the blowup. Too strange.

Thanks

Temp local tables are notorious database bloaters. Adding and deleting
records in temp tables will make your database file quickly grow. Put your
temp tables in a separate external database and link to the tables. Make a
copy of the database and save it. Each time you need to delete records and
add new records, delete the temp database file, make a new file from your
copy and then populate the tables.

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
Over 1175 users have come to me from the newsgroups requesting help
resource@pcdatasheet.com



"DFS" <nospam@dfs_.com> wrote in message
news:fU8_f.4041$Za3.474@bignews7.bellsouth.net...[color=blue]
> Largish system, was 13mb (after de/compile and compact/repair)
>
> It's mostly forms, queries and code. About 40 local tables (with tiny
> numbers of records, like 1 to 10)
>
> Recently added a few more TEMP* local tables (no records) and a couple of
> screens and a few hundred lines of code
>
> Now it's 44mb after de/compiled and compact/repair!
>
> Another odd thing is a routine that was taking 5 or 6 seconds to run while
> building it started completing in 3 seconds. As if the entire routine was
> cached.
>
> I don't mind creating a new file and importing everything, but I'd like to
> know what caused the blowup. Too strange.
>
> Thanks
>
>[/color]

PC D wrote:[color=blue]
> Temp local tables are notorious database bloaters. Adding and deleting
> records in temp tables will make your database file quickly grow. Put your
> temp tables in a separate external database and link to the tables. Make a
> copy of the database and save it. Each time you need to delete records and
> add new records, delete the temp database file, make a new file from your
> copy and then populate the tables.
>[/color]


--
To anyone reading this thread:

It is commonly accepted that these newsgroups are for free
exchange of information. Please be aware that PC Datasheet
is a notorious job hunter. If you are considering doing
business with him then I suggest that you take a look at
the link below first.

http://home.tiscali.nl/arracom/whoissteve.html

Randy Harris

PC D wrote:[color=blue]
> Temp local tables are notorious database bloaters. Adding and deleting
> records in temp tables will make your database file quickly grow.[/color]

I know, but until now deleting the records and compact/repair has always
shrunk it down to normal. All of a sudden it won't.

Why?


[color=blue]
> Put your temp tables in a separate external
> database and link to the tables.[/color]

I've done that on several other systems. Might have to try it here, too.


Thanks



[color=blue]
> Make a copy of the database and save it. Each time you need
> to delete records and add new records, delete the temp database file,
> make a new file from your copy and then populate the tables.[/color]



[color=blue]
> "DFS" <nospam@dfs_.com> wrote in message
> news:fU8_f.4041$Za3.474@bignews7.bellsouth.net...[color=green]
>> Largish system, was 13mb (after de/compile and compact/repair)
>>
>> It's mostly forms, queries and code. About 40 local tables (with
>> tiny numbers of records, like 1 to 10)
>>
>> Recently added a few more TEMP* local tables (no records) and a
>> couple of screens and a few hundred lines of code
>>
>> Now it's 44mb after de/compiled and compact/repair!
>>
>> Another odd thing is a routine that was taking 5 or 6 seconds to run
>> while building it started completing in 3 seconds. As if the entire
>> routine was cached.
>>
>> I don't mind creating a new file and importing everything, but I'd
>> like to know what caused the blowup. Too strange.
>>
>> Thanks[/color][/color]