I was just wondering what some best practices for finishing it off are.
I can throw in a few suggestions based on my outdated 2007 version:
- always have back up files (consider a nightly backup of the back end tables)
- if you didn't split it at the beginning you should have. Not too late.
- compile the front end into an accde (assuming that's still the current compiled extension)
- specify the main form to be loaded on startup
- give the app a title (spec'ing an icon adds a nice touch, but was always a pain for me since network gods archived unused files; i.e. bmp files used by db)
- uncheck 'use Access special keys'
- uncheck display Navigation pane
- have an About form with a not obvious label (say version number) that accepts a double click to cycle the AllowBypass key property
- link the back end tables with a password (not iron clad - connection password can be found if you know how) but it keeps most people from seeing the tables
- I use 'overlapping documents' setting if I want to control the form size
- If each user has their own FE (preferred method) a startup routine should check that their FE copy is current (by checking the version number you update in a BE table after each design modification to the FE) and have the db download the new version - or at least, don't let them use outdated versions.
Is there anything I need to do to make it universally ready for just about any environment?
That's a tough one. Anything can happen from not having the db in trusted locations to users who don't have proper network permissions to locations of code libraries (references) to bad or slow connections to...
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.