I have decided to add a document control app (DC) I built previously to the manufacturing production application (HSI) I am nearing completion. I thought it best not to completely meld them, but partially. I think for the most part, it will be simpler and more expedient to run DC in a stand alone position with some access retrofitting and testing to link DC with HSI than to fully integrate all the components of DC into the parent HSI. So here is what I have done that I need advice on whether this is really against best practice and/or there are defects in my logic and pitfalls present in my strategy.
1. I placed the folder holding the DC app files and supporting folders under the HSI folder, so the HSI folder contains ALL app files and folders. There is a toolbar button on the Main Menu in HSI that opens DC.
3. The two apps DC and HSI have many common utility scripts (UDFs) that I need to tailor and unify (color schemes, input variable names, output variable names, etc) to be utilized by both apps. To centralize these scripts so accessible to both applications, I created a third "application" I named "Shared_db" (Shared) having only the abd, alb,alm,alx files, in a folder under HSI. I placed all the common scripts in that app and added the library for Shared into DC and HSI. This makes the scripts all accessible within both apps and changes can be made to the scripts whether in either HSI or DC.
4. The DC app needs access to the Staff table for passwords and things that is in the HSI folder so I added this table to DC app. I got the warnings about tables not in root folder but I allowed it.
Sound reasonable?
1. I placed the folder holding the DC app files and supporting folders under the HSI folder, so the HSI folder contains ALL app files and folders. There is a toolbar button on the Main Menu in HSI that opens DC.
3. The two apps DC and HSI have many common utility scripts (UDFs) that I need to tailor and unify (color schemes, input variable names, output variable names, etc) to be utilized by both apps. To centralize these scripts so accessible to both applications, I created a third "application" I named "Shared_db" (Shared) having only the abd, alb,alm,alx files, in a folder under HSI. I placed all the common scripts in that app and added the library for Shared into DC and HSI. This makes the scripts all accessible within both apps and changes can be made to the scripts whether in either HSI or DC.
4. The DC app needs access to the Staff table for passwords and things that is in the HSI folder so I added this table to DC app. I got the warnings about tables not in root folder but I allowed it.
Sound reasonable?
Comment