---
title: "\"Related Leases\" tab - Leases not showing"
canonical: "https://servicedesk.maxgeo.com/space/LC/1263304768/%22Related%20Leases%22%20tab%20-%20Leases%20not%20showing"
format: markdown
---
<u>**Problem:**</u>

1. When I go to the "Related Leases" tab there are none showing.  Refer **Cause 1**.
2. After I add new Leases to the "Related Leases" tab, I get an error message and note that not all Leases were added.  Refer **Cause 2**.
3. After I add new Leases to the "Related Leases" tab, a message is generated saying the Leases have been added, however these new Leases aren't showing.  Refer **Cause 3**.

<u>**Cause:**</u>

1. Most likely, Leases have not been assigned.  Refer **Solution 1**.
2. The missing Leases are already recorded against this Agreement.  Refer **Solution 2**.
3. They haven't been pulled through to the grid.  Refer **Solution 3**.
4. The user has insufficient SQL permissions, and therefore is unable to execute stored procedures.  Refer **Solution 4**.

<u>**Solution:**</u>

1. Assign Leases to this Agreement, as per the HelpManual.  You may wish to request training or mentoring via[ sales@maxgeo.com](mailto:sales@maxgeo.com)
2. If you can see them, problem solved.  If you can't, refer **Cause 3**.
3. Reset the grid.  If this doesn't resolve the issue, refer **Cause 4**.
4. There are detailed instructions in the related article "[creating executable permissions in SQL](https://maxgeo.atlassian.net/wiki/spaces/LC/pages/1263566934)"

<u>**Additional Info:**</u>

- <u>*How do I reset a 'grid'?*</u>  Refer to related article "[Resetting Grids](https://maxgeo.atlassian.net/wiki/spaces/LC/pages/1263665205)".
- <u>*What is a 'stored procedure'?*</u>  It is a set of instructions that are triggered by a particular action - usually within the software.  For example, completing an Action.  Where these instructions are stored within the database, the user requires sufficient permissions to execute them.
- <u>*What wasn't it an issue in an earlier version of LeaseControl*</u>?  Older versions had limited functionality, therefore certain rights were required.  It may be interesting to note that this is only required where SQL permissions have been specifically restricted.