Incredible Growing database....

[jonceramic]

Hi All,

I have a database which uses a lot of linked tables from the front-end
to both Access and Oracle backend tables.

I was just doing fine for months, until I created a new set of forms
and a few new tables.

Now, whenever I issue out my front end, it starts bloating out and
grows like crazy. My normal 7MB file is currently, with one user, a
125MB file!

I've tested, and it's every time I edit in a window that merges Access
and Oracle data together. And they edit a record from that query.

Problem is, it looks just like the other kind of queries I've always
done. There's a few calculated fields in the database.
(concatenating a firstname/lastname together from Oracle into a "full
name". And, a sorting field created by a math equation using the -1
from an Access yes/no field. That sort of thing.) But, these are all
things I've done in the past.

Any hints or helps on what might be going on? (Compacting fixes it.)

My Access backend file with the actual data stays nice and slim. So,
I assume there's some sort of caching going on to deal with locks or
"dynasets" or queries or something.

TIA,

Jon

[Tom van Stiphout]

On Tue, 21 Oct 2008 12:26:36 -0700 (PDT), jonceramic
<jo********@gmail.comwrote:

No, this is a credible report, not an incredible one.
Except for a few well-known situations you cannot control the
increasing size of an Access db. Take solace in the fact that at 125MB
it is still only one promille of a typical small and cheap hard drive.

-Tom.
Microsoft Access MVP

>Hi All,

I have a database which uses a lot of linked tables from the front-end
to both Access and Oracle backend tables.

I was just doing fine for months, until I created a new set of forms
and a few new tables.

Now, whenever I issue out my front end, it starts bloating out and
grows like crazy. My normal 7MB file is currently, with one user, a
125MB file!

I've tested, and it's every time I edit in a window that merges Access
and Oracle data together. And they edit a record from that query.

Problem is, it looks just like the other kind of queries I've always
done. There's a few calculated fields in the database.
(concatenating a firstname/lastname together from Oracle into a "full
name". And, a sorting field created by a math equation using the -1
from an Access yes/no field. That sort of thing.) But, these are all
things I've done in the past.

Any hints or helps on what might be going on? (Compacting fixes it.)

My Access backend file with the actual data stays nice and slim. So,
I assume there's some sort of caching going on to deal with locks or
"dynasets" or queries or something.

TIA,

Jon

[Keith Wilby]

"jonceramic" <jo********@gmail.comwrote in message
news:5f**********************************@k16g2000 hsf.googlegroups.com...

>
Now, whenever I issue out my front end, it starts bloating out and
grows like crazy. My normal 7MB file is currently, with one user, a
125MB file!

If you delivered a new, pristine FE file with every user-launch (for example
using a batch file) would it matter how much bloat there was? I must
concede I don't know why it would bloat at all unless your users are working
under the hood/bonnet.

Keith.
www.keithwilby.co.uk

[jonceramic]

On Oct 22, 8:43*am, Tom van Stiphout <[e-mail]:

On Tue, 21 Oct 2008 12:26:36 -0700 (PDT), jonceramic

<[e-mail]:

No, this is a credible report, not an incredible one.
Except for a few well-known situations you cannot control the
increasing size of an Access db. Take solace in the fact that at 125MB
it is still only one promille of a typical small and cheap hard drive.

-Tom.
Microsoft Access MVP

Thx Tom. I would take solace, except for the fact that this is on a
shared, citrix network running at multiple sites and IS is hitting the
SAN limits. :)

Kinda bugs me that it was fine until I did "something different", but
don't know what that was.

Either way, checking the "compact on close" option knocks the size
back down to, well, size. :) So, that's just 2 seconds of time on
shutdown.

Jon

[jonceramic]

On Oct 22, 9:35*am, "Keith Wilby" <[e-mail]:

"jonceramic" <[e-mail] in message

news:5f**********************************@k16g2000 hsf.googlegroups.com...

Now, whenever I issue out my front end, it starts bloating out and
grows like crazy. *My normal 7MB file is currently, with one user, a
125MB file!

If you delivered a new, pristine FE file with every user-launch (for example
using a batch file) would it matter how much bloat there was? *I must
concede I don't know why it would bloat at all unless your users are working
under the hood/bonnet.

Keith.www.keithwilby.co.uk

That's what bugs me. No bonnet work. I haven't gone the batch file
route (see above reply regarding "compact on close" to generate the
same effect.)

I'm assuming it has something to do with local FE caching of query
results that join a linked Access table and an ODBC linked Oracle
table - where I edit records in the Access table through that query.
But seeing as I've done that sort of thing before, within this app, I
feel powerless for trying to trouble shoot without just knocking out
functionality until I hit on the issue.

Jon

[bobh]

On Oct 21, 3:26*pm, jonceramic <[e-mail]:

Hi All,

I have a database which uses a lot of linked tables from the front-end
to both Access and Oracle backend tables.

I was just doing fine for months, until I created a new set of forms
and a few new tables.

Now, whenever I issue out my front end, it starts bloating out and
grows like crazy. *My normal 7MB file is currently, with one user, a
125MB file!

I've tested, and it's every time I edit in a window that merges Access
and Oracle data together. *And they edit a record from that query.

Problem is, it looks just like the other kind of queries I've always
done. *There's a few calculated fields in the database.
(concatenating a firstname/lastname together from Oracle into a "full
name". *And, a sorting field created by a math equation using the -1
from an Access yes/no field. *That sort of thing.) *But, these are all
things I've done in the past.

Any hints or helps on what might be going on? *(Compacting fixes it.)

My Access backend file with the actual data stays nice and slim. *So,
I assume there's some sort of caching going on to deal with locks or
"dynasets" or queries or something.

TIA,

Jon

The 'few new tables' you created, where do they reside, your Access
FE or your Access BE or Oracle???
bobh.

[jonceramic]

On Oct 22, 11:51*am, bobh <[e-mail]:

On Oct 21, 3:26*pm, jonceramic <[e-mail]:

Hi All,

I have a database which uses a lot of linked tables from the front-end
to both Access and Oracle backend tables.

I was just doing fine for months, until I created a new set of forms
and a few new tables.

Now, whenever I issue out my front end, it starts bloating out and
grows like crazy. *My normal 7MB file is currently, with one user, a
125MB file!

I've tested, and it's every time I edit in a window that merges Access
and Oracle data together. *And they edit a record from that query.

Problem is, it looks just like the other kind of queries I've always
done. *There's a few calculated fields in the database.
(concatenating a firstname/lastname together from Oracle into a "full
name". *And, a sorting field created by a math equation using the -1
from an Access yes/no field. *That sort of thing.) *But, these are all
things I've done in the past.

Any hints or helps on what might be going on? *(Compacting fixes it.)

My Access backend file with the actual data stays nice and slim. *So,
I assume there's some sort of caching going on to deal with locks or
"dynasets" or queries or something.

TIA,

Jon

The 'few new tables' you created, where do they reside, *your Access
FE *or *your Access BE *or *Oracle???
bobh.- Hide quoted text -

- Show quoted text -

Access BE and Oracle. No FE tables used.

Jon