[AccessD] notes on mdb bloat

Hi Seth

What happens if you "forward port" the A97 version to A2000?

/gustav


> Greetings,

> Just wanted to share an observation with y'all.  We have one app which
> needs both A2K and A97 versions.  It's not a big deal.   It just means
> that every time we make any changes to the FE, wee need to back-port it
> to A97 using the built-in tool.  Before I do this, I always run a
> compact-and-repair first.  Having done this several times now, I have
> noticed two things.

> 1) The conversion process seems to take an inordinately long time.  I
> haven't timed it, but it seems to take at least 5 minutes, if not
> longer.  This is not a large or complex app.  It's a bit sloppy (I
> inherited it from a previous, inexperienced Access user), but I've fixed
> a lot of that.  It's not a big deal, I just start it and then check on
> it until it's done.  Not a big deal, but I'm wondering what the hangup
> is.

> 2) The A2K FE mdb is currently right around 2MB.  The A97 FE mdb is just
> under 600KB.  What the heck does A2K require in the file that adds that
> much overhead?  Like I said, this is not a terribly complex or large
> app.  This is also not a big deal, it just takes longer to download
> updates to the users' computers.

> I'm not really looking for answers here, just wanted to share what I've
> observed.  If anyone can corroborate this experience and has some ideas,
> I'd be interested from an academic standpoint to see what you think.

> Share and enjoy!

> Seth