Tip:
Highlight text to annotate it
X
Ace contains
configuration data and, therefore, if you want to
maintain the integrity of that data through
any kind of hardware loss or
failure, you will need to do a -- to create a backup.
Now, ACE has three ways in
which data can change. You have the source
code of your ACE Modules or projects, and
we leave this up to the developers to be responsible
for these files. You can use Visual Source Safe
or any other standard mechanism for keeping
these files backed up and-or up to date.
There's also the compiled code of ACE Modules, and this is,
this would be the executables and DLL's.
And they only change
when the code is, is recompiled, so
you can either regenerate everything
from your original ACE Modules, or keep a backup
of your ACE Modules, your,
your compiled code directory, whether that be
executables or, or DLL's. And then, finally,
we have the entries in the Module Database. And the entries in the Module
Database are backed up when the
PI backup occurs. So, as long as you are
keeping your PI backup up to date, you will
have the entries in the PI Module Database.