I am looking at a new database that I inherited and I am exploring options to reduce the overhead.
There is a macro that runs every time that the form closes. This is a waste. I moved it to a button. But what I discovered is that the macro behind the button has some objects that I may be able to remove and create and use in other ways.
For example, there is a query that creates a table named LU_Name which is being used a source for a combo box. then later in the macro the LU_Name table is being used in a query.
For my question;
I can use a select statement for the combo box to get the needed data for the combo boxes and use the main table that created the LU_Name to be used in the query later on.
What do the pros suggest is the most efficient in this case? The macro makes about 6 tables and appends some of them with other queries.
Do developers avoid creating objects, or are they a necessary evil?
Posted by: email@example.com
|Reply via web post||•||Reply to sender||•||Reply to group||•||Start a New Topic||•||Messages in this topic (1)|