Database design · Laboratory systems

Laboratory Database & Administration

Access/VBA laboratory-record development following the offline kiosk prototype, now handed to a coworker.

During aerospace laboratory role · Development handed offAccess/VBA contribution · Development handed off

Overview

The laboratory moved from a custom Ubuntu kiosk toward Microsoft Access on Windows so coworkers could more easily maintain its records and workflows. I learned VBA and developed interfaces and SQL queries around the laboratory engineer’s initial database, translating laboratory needs into linked records and administration flows. Sign-in/out was informally estimated at one to two minutes versus five or more for the old Google Form. Continued development has been handed to a coworker; final deployment, sustained adoption, and formal workflow testing remain unconfirmed.

My Contribution

I learned VBA, developed the Access interface and SQL queries around the laboratory engineer’s initial database, and helped translate laboratory needs into relationships and workflow structure. This followed the Python/Kivy prototype. Continued development has been handed to a coworker.

Engineering Approach

The focus was linking related records and building usable data-entry and administration flows in a platform the laboratory staff could continue developing.

Results & Current Status

The old Google Form could take five minutes or more; sign-in/out through both the Python/Kivy prototype and the Access workflow was estimated at approximately one to two minutes. These estimates came from experience and were not formally timed. My active Access work has been handed off; final deployment, sustained adoption, and formal workflow testing remain unconfirmed.

Next Steps

  1. Add a public schema diagram and representative screens from the latest Access version, with the coworker’s contribution credited.
← Aerospace Lab projects