Good Day,
The "DisplayMSACCESSSetup()" sub-routine needs the following changes to be fully compliant with the "instance" functionality.
) add strTable to the Dim statement
) assign [strInstance & "PageLog"] to strTable
) use strTable as input for GetLogDate
) use strTable as input for CountRecords
) set "table" form's hidden field to strTable
Regards.
Running MetaTraffic V 1.200 b 3
"Instance" support for MsAccess
Hello,
I didn't include "Instance" support for MS Access because I thought it would be better to use a separate MS Access database if you were going to run it on several sites, specifically when it came to performance.
Regards,
~Chad
"Instance" support for MsAccess
Good point,
I understand that it would be useless to use the same database for multiple sites, specially with MsAccess, however just to ensure consistancy in the code I think that would be appropriate.
With MsAccess, the instance could be used as an indicator to re-route records to a given table while archiving is ongoing on the "inactive" table.
So for instance, I having 2 tables in the same db, one prefixed and the other not, it would become possible to archive the data in another DB from the larger table (the non-prefixed one) in another database, while site logging is still active (using the prefixed one).
The logging would only needed to be de-activated while the compaction is done after the removal of the archived records, and the data from the "prefixed" table would then move over to the non-prefixed one thus minimizing the downtime of the application availability.
In the setup page, I'm about to create links to toggle the logging, and instances to accomodate that scenario, thus eliminating the need to change the config.asp file to switch from one scenario to another.
The links would actually copy pre-defined config files via FSO. Simple but effective as it minimizes the uploads with FTP when maintenance is planned.
BTW, I extended a bit the Login functionality scope, supporting more than one user. Also, for each user there is a flag indicating if they have access to the setup section where the records can be delete or the database be compacted. Usefull if you want to protect the data from some adventurous users.
Regards.