ACCESS Performance

[amazo]

Dear all,

I don't know if my question is Access Version related specific or
applies to any, anyway here it is:

Regarding Access performance, memory consuming resources, etc., which
is better? ...

.. to have a "hide" form with, let's say, 50 fields to store values to
exchange information among forms, queries, reports, etc. while
application is up.

.. ... or to have 50 public memory variables.

Thanks in advance.

Angel.

 

[Allen Browne]

The variables will use less memory and be faster to access than the form,
but when users have hundreds of MB of RAM and gigahz of CPU speed, the
difference is probably mimimal.

The values in the hidden form are easier to develop and debug, i.e. they are
not lost every time you reset your project during development. Additionally,
you can use the Close event of the hidden form to simulate an application
close event.

 

[Salad]

Dear all,

I don't know if my question is Access Version related specific or
applies to any, anyway here it is:

Regarding Access performance, memory consuming resources, etc., which
is better? ...

. to have a "hide" form with, let's say, 50 fields to store values to
exchange information among forms, queries, reports, etc. while
application is up.

. ... or to have 50 public memory variables.

Thanks in advance.

Angel.

I usually have a table, something like AppVariables. 1 record, a bunch
of fields. That works fine.

If you use variables, none of your code can error out to Debug/End mode.
If that happens, you need to reset the variables.