Asset Management database with gui and input format restrictions

What it is:

This is an example Software Asset Management (SAM) database with a gui that can prevent incorrect data from being entered.
Database reports can be produced in JSON and CSV formats and automatically open.

How it’s used:

First, set the database filepath and name, and the folder where you want reports saved, in a .env file. Next, run
sam_gui.py, the input section. If starting with an empty database, the only option that will work is “Add Software Vendor.”
serial_formatter.py is configured to enforce correctly formatted serial number entries for the fictional companies
Abalobadiah and OAuthDex, and correctly formatted product key entries for OAuthDex. The example database contains sample
data matching the RegEx restrictions for these companies.

Why it should be used:

Malformed audit data is a common source of confusion and wasted time in the audit analysis process.
Bad data can be introduced in many ways (typos, poor packaging scans, incomplete copy/paste), and it’s good to catch it
before it ever enters the SAM system.

Why it shouldn’t be used:

This project is currently in a demonstration/proof-of-concept phase. There is only one database table with four columns.
A more complete SAM application might have a system of checking licenses in and out to employees.
It’s also not possible to write regular expressions for every product code for every product line for every vendor that’s
ever existed or will exist. There are ideas in here, particularly some neat PySimpleGUI tricks, that can be incorporated
into other projects.

Application gui with with DB Browser for SQLite in the background.

Serial numbers and product keys that don’t match defined formats will prompt re-entry.

A detailed explanation of handling displayed data and hidden data is in my repository

Button width is set to the longest vendor name.

Listbox width is set to the longest row of displayed data.

Listbox height is set to the length of the list of vendors with a maximum length of 20.

The maximum number of buttons in a row is 9.

Known issues:

• Individual vendor report file names incorporate vendor names. The file creation process may fail if there are special
  characters in the vendor’s name. Avoid using special characters, especially backslashes.
• There is no method to delete data, but cells can be over-written with empty strings except where format validation is enforced. Edit database directly in another application.