If I may jump in to add my two cents...Forms and reports are objects in Access. As with all Access objects, when an object is created it is built using code. Much of that code is a template that holds places for various items (controls) in that object. The code is then rendered into a viewable item. To present a form or report, the compiler compiles the code that makes up the object.
One thing that many Access users don't realize is that if you put a control on a form and later delete that control the code for it remains in the form's metadata. This eventually leads to all kinds of bloat. I long ago got into the habit of keeping an eye on the file size of any Access project I was developing. When the size became unreasonable I simply imported everything into a new, blank database. That strips out all that useless code and brings the file size back down to a reasonable size. That process also strips out all the unseen garbage in the code pages and boosts performance.
I created a utility called ExportAll for this very purpose.
On Mon, Oct 4, 2021 at 02:00 PM, <drnorbert@gmail.com> wrote:
Dear Crystal,
Sorry, you are correct I meant 1999, the inception of Access version 1.0 was on 11/ 1992.
I am still puzzled about what creates the Binary Data in forms and reports even though they don't have an image included.
Regards,
Norbert
--
Regards,
Bill Mosca, Founder - MS_Access_Professionals
Microsoft Office Access MVP 2010-2016
My nothing-to-do-with-Access blog
_._,_._,_
Groups.io Links:
You receive all messages sent to this group.
View/Reply Online (#116074) | Reply To Group | Reply To Sender | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [sugeng.panjalu.access@blogger.com]
_._,_._,_
Tidak ada komentar:
Posting Komentar