Surely some of the older records could be archived split the database and have links to several back ends to view old records if required? this could then reduce the overall size of each to a manageble amount but 50gb for text and numbers.... you say the companies being going a long time were the original records punched cards lol
The question of logos in dbs can create a massive increase in db size.
Case 1:
The logo was a .jpg file, 176Kb. When embedded in the db it blew the db out by an extra 35Mb - I couldn't believe it. If this was embedded many times in various frms/rpts the db would be massive.
Case 2:
I noticed an fe looking quite large for what it had in it - again, a logo problem. The logo had been created in Word.
I managed to solve both these problems reasonably satisfactorily (still keeping the logo embedded) - in both cases I converted the files to .bmp. Before that I emailed the .jpg files to myself using Netscape and the "keep picture small" option. This reduced both of the above to about 15% of the original file size.