I understand that you are using the 'Standalone' or 'Flat file' system and so you don't need a separate database server. So why are you being told that NoiseMap can't find the server and why are you asked to contact the administrator?
First, it is important to understand that although you don't use a database server (and therefore you don't have a database administrator either), the 'Flat file' is still a database: even though it is a self-contained one that looks like an ordinary Windows file. In fact, when you 'commit changes' to the 'database', NoiseMap uses a special 'driver' to write these changes into the database file. (That's why NoiseMap says 'commit' rather than 'save'.) In fact, as part of the NoiseMap installation, this special driver is copied to your computer and it manages all the database communication between NoiseMap software and your computer.
So there are at least two possible reasons for getting this error message. The first is that the database driver has not been correctly installed (and you should have seen an error screen informing you of this.) If you have never been able to start NoiseMap, this is the most likely cause of the problem and you should repeat the installation, making sure you have full administrator privileges first.
If NoiseMap has been working and this message appears, the most likely cause is that the connection between your computer and the database file has been lost. The connection is established when you first connect to the database and must remain open until you exit NoiseMap. But many networks will 'time out' a connection that has not been used for a while. This is the usual reason for the problem. You need to contact your network administrator to ask them to extend the timeout to a long period. Alternatively, locate the database file on your own hard drive and just back it up to the network daily (using Windows' file copy).
If your computer hangs with this message, you may be able to crash out of it in which case when you restart NoiseMap, you may be able to recover the backup file and then commit any changes back to the database.
