When the Troika program is running it does various bits of work with the front end mdb. This processing causes the mdb to grow in size (temp tables, queries etc) so when the program is closed MSAccess compacts and repairs it, to avoid never-ending bloating.
Assuming it is the Wealth Management program in use, the process creates a Database.mdb (which is a compacted and repaired copy of the fpsTroik.mdb, and when it is finished it replaces the current db with the Database.mdb renamed to fpsTroik.mdb. It is the same process for other modules, but the name of the individual mdb files differ. For example, when closing the Troika Administrator module, it would be looking to compact and repair the fpsTrSec.mdb instead.
The presence of Database.mdb files within a user's local directory (Database1.mdb, Database2.mdb etc.) suggests that this process is being interrupted occasionally, and as a consequence these files are left behind:
This interruption can be when users are logging off prior to the compacting process completing, or network issues forcing a close of the program.
Ultimately, they are no longer needed, and they are able to be deleted.