Have I Created a Monster?

  • Thread starter Thread starter S Jackson
  • Start date Start date
S

S Jackson

After several months and many tears, tantrums and trials, I think I have
completed a trial version of a case management database that our Legal
Services Division will use to manage administrative cases.

I have not split the database at this point because I am going to send out
complete stand-alone copies to a few legal assistants to give it a "try" and
provide feedback/changes (groan!).

I ended up with a database that is 4,428 kb in size. Have I created a
monster? Is this huge for a database application?

TIA
S. Jackson
 
Only about 4MB? How did you keep it so small? I suspect they will be wanting
you to add a lot of items, especially different reports, to cover various
situations they come up with.

Several hundred megabytes is not unusual with a lot of data also added.
Front-ends up to 50 megabytes are not unusual, especially if you have
graphics on the forms or reports. I'm sure some folks on this newsgroup have
made even larger ones.
 
No - this is tiny. My primary application (FE alone) is approx 32 mb. The
backend is 140mb. A single database can go up to 2Gig so you've got a long
way to go!
 
Hello S Jackson,
No! You have not created a monster.
As time goes on you will add data and updates to your
queries, forms, reports, etc. and you will see the db
grow. Just remember to compact and repair it often.

Just for your information, I have one Access Front-
end .mdb that is 60+Megabytes and it is still growing. I
compact and compile it every time I update it and then
distribute it; keeping at least three 'boilerplate' copies
on two servers and My System (remember Murphy's Law).

Hope this helps, Pete
(e-mail address removed)
 
You might have created a monster if you didn't normalize the tables. That
would be the first potential trap to evaluate. You'll find out pretty quick
as soon as users start saying: "Now, can you make it do THIS?"
 
Wow! Thanks for all the responses. Now I'm worried that I have created a
dud! LOL! Oh well, I'm sure I am going to receive a lot of feedback. It
is the first application that I've created with this much automation in it.
Thanks to all you great folks here for help along the way!

S. Jackson
 
I ended up with a database that is 4,428 kb in size. Have I created a
monster? Is this huge for a database application?

<checking>

I've got frontends of 14.5 MByte, 11 MByte and 8 MByte - these have NO
table data at all, or just tiny administrative tables.

Access is a hog for disk.

You can (and probably should) do some cleaning up, which may well
shrink this a fair bit, nonetheless. Create a new, empty database, and
use File... Get External Data... Import to import everything. Unselect
the option to import Relationships; after importing the tables, go
into the relationships window and recreate them (there seems to be a
bug in imported relationships renaming indexes). Compact and Repair
the resulting database. This will get rid of some of the leftover
"stuff" that Compact and Repair doesn't, and should make the database
smaller, faster, and more stable.
 
No...must...not...make...joke...

You know.. my front end is only 1.4 MB... no wonder I feel so inferior!

And maybe that's why I keep getting those emails! <g>


Fred Boer

P.S. No self control at all... tsk, tsk...
 
Congratulations, Shelly. You have reached an important milestone with your
case management system and I'm happy to hear that you now have it in the
"user testing" phase. Your willingness to adopt new or unfamiliar
techniques suggested here and your tenacity in asking the questions needed
to make these techniques your own are great qualities.

Good luck with your project as you continue its deployment

and PD: split that database <smile>
 
Congratulations, Shelly. You have reached an important milestone with your
case management system and I'm happy to hear that you now have it in the
"user testing" phase. Your willingness to adopt new or unfamiliar
techniques suggested here and your tenacity in asking the questions needed
to make these techniques your own are great qualities.

Good luck with your project as you continue its deployment

Agreed! Well said Cheryl.
and PD: split that database <smile>

AGREED!!! said:
Cheryl Fischer, MVP Microsoft Access

and HOORAY, congratulations! Good to see that in your .sig!!
 
Thanks so much!

--

Cheryl Fischer, MVP Microsoft Access
Law/Sys Associates, Houston, TX
 
No...must...not...make...joke...

You know.. my front end is only 1.4 MB... no wonder I feel so inferior!

And maybe that's why I keep getting those emails! <g>

Now, now... you know it's not the size, it's how you use it!
 
Back
Top