> For the complete documentation index, see [llms.txt](https://docs.k2geospatial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.k2geospatial.com/en2/administrator/jmap-server-administrator-manual/spatial-data-sources/vector-data-sources/personal-geodatabase.md).

# Personal geodatabase

<table data-header-hidden><thead><tr><th width="193.5"></th><th></th></tr></thead><tbody><tr><td>Read</td><td>Yes</td></tr><tr><td>Write</td><td>Yes</td></tr></tbody></table>

JMap Server can read ESRI Personal geodatabases to extract spatial and attribute data to be used as a spatial data source. This format uses Microsoft Access files to store the data. The connection to the Access database must already be configured using the MS Access driver. See [Creating Databases](/en2/administrator/jmap-server-administrator-manual/databases/creating-databases.md) for more information on this topic.

<table data-header-hidden><thead><tr><th width="191.5"></th><th></th></tr></thead><tbody><tr><td><strong>Parameters</strong></td><td> </td></tr><tr><td>Database</td><td>Select the database to read the data from. This database must connect to an MS Access file. It must already be configured in JMap Admin.</td></tr><tr><td>SQL query</td><td>Enter the SQL query used to extract geometries and attributes from the database.</td></tr><tr><td>Geometry table</td><td>Select the physical table that effectively contains the geometries. Pressing <strong>Load</strong> will retrieve the list of fields returned by the query. This is necessary for the rest of the configuration.</td></tr><tr><td>Id field</td><td>Select a field that contains unique identifiers. Only integer fields are listed. The field is usually called OBJECT_ID.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.k2geospatial.com/en2/administrator/jmap-server-administrator-manual/spatial-data-sources/vector-data-sources/personal-geodatabase.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.