What is the purpose of .ADM files?

When the catalogue is opened it creates an file with an '.adm' extension in the same folder and with the same name as the '.FDB' catalogue file. The 'adm' file should disappear when the last user closes the catalogue.

What does this 'adm' file do?
The function is not documented but essentially is seems to be to do with use of the Catalogue and mutliple access mode. Most likely the client checks for the presence of and status of the .adm file to ascertain the usage status - e.g. if there is an ADM flag user #2 can't go to admin mode. As v7 dropped non-Server based multi-user access, I wonder if ADMs may get dropped in due course (but I suspect they are part of the underlying C-Tree database schema).

The catalogue is closed, and the '.adm' file is there, can I delete it?
Yes.

I tried deleting the '.adm' file but the OS gives a warning it is in use...
In order:

• Check the catalogue is not actually open in another client - if so close the catalogue there as well. Try deleting again.
• Close the whole Portfolio client program as well as the catalogue (server can stay running if in use). Try again
• Worst case, re-boot the OS, as this will clear the file lock.

You may also notice, especially on Windows OS, that you can close a catalogue file but not then edit it or move it while the client is still open. It seems in some - not all (grr!) - circumstances that Portfolio doesn't 'release' the catalogue file back to the system -i.e. unlock it - until the client closes; closing the client (and re-opening if necessary) solves this.

Do I need to copy this file when moving a Catalogue or burning it to CD?
No, you may safely ignore it as Portfolio will recreate the file if it needs to do so.

Question: What is the purpose of .ADM files? [FAQ00234.htm]
Last Update:- 24 September 2007

This FAQ is created and maintained using

Friday - The Automatic FAQ Maker