The symptoms are clear. You attempt to import a GIS layer into XMap and the only options in the database list are “Other” and “New.” “Where is my database?,” you ponder. “What happened to all of my other layers?” It feels like someone has walked into your office and removed the filing cabinet containing all of your important documents. “What do I do now? Where’s the panic button?”
Fortunately, the solution to this temporary predicament is usually quick and painless. The panic button is not needed.
The problem stems 
from the fact that XMap employs a Microsoft SQL database to store GIS data and occasionally, for reasons often too complex and bewildering to explain here, XMap refuses to “talk” to SQL and vice versa. The problem is easily solved by reintroducing both parties.
This reintroduction can be initiated in XMap from either the Manage Layers or the Import Layer window, both of which are accessed by clicking the Layers button above the Workspace table. In either case, select Other from the database drop-down list to display the Attach Database window.
Usually, the errant
SQL server will be listed in the server drop-down list and will appear as either (LOCAL)\XMAP* or [your computer name]\XMAP* (* represents the version of XMap on your computer). If this is the case, simply select the server from the list, make sure Windows Authentication is checked, and click the Connect button. After a few seconds, the database list will display all of the XMap databases on your local server. For new XMap users, this list will be limited to the preconfigured database entitled DeLormeSampleDB. After selecting this or any other available database, click the OK button and continue importing or managing your layers as before.
It is likely that most of you can now stop reading this article and go back to work, secure in the knowledge that you have solved your database connection problem. However, there is a small group of you who will probably want to read on for the simple reason that your server list in the Attach Database window is conspicuously empty and you could not perform the succeeding steps.
If you are one of those unfortunate XMap users, there is an additional but very simple step that must be taken. In the blank server window, type (LOCAL)\XMAP* (* should be either 7, 6, or 5 depending on the version of XMap that was first installed on your computer and, correspondingly, the version of SQL that was created) and continue with the steps outlined above.
On rare occasions, the two solutions described will fail to rectify the database connection issue; this is usually because the SQL service is not running. Often, this problem occurs after an update to your operating system during which Windows fails to restart the service. The solution for this problem takes place outside of XMap.
- From the Start menu,
right-click My Computer and select Manage. - Click the plus sign next to Services and Applications and click Services.
- In the Services window, right-click SQL Server (XMAP*) and choose either Start or Restart.
Your database should now be available in XMap.
If the XMap instance of SQL is not listed in the Services widow, you will need to reinstall it from your XMap install disk. Instructions are available here.
Thankfully, the solutions for the common XMap database connection problems are reasonably straightforward and usually the disconnection problems will not reoccur.
