Jan 05 2020 09:23 AM
Jan 06 2020 04:47 AM
Jan 06 2020 05:12 AM
I see. That actually sounds a little like a high-level project spec doc you might give to a contractor you hire to do the work.
What SPECIFIC part of that have you tried so far?
What SPECIFIC part of that have you had trouble implementing?
Jan 06 2020 05:16 AM
Jan 06 2020 05:19 AM
Jan 06 2020 05:26 AM
I'm sorry, I don't mean to be negative, but that's a really big topic.
The direct answer is, "Yes, most of this could be done in Access."
You'll be able to build a set of relational tables to store your data. That's the primary reason for using Access.
You'll be able to build forms to support interaction between the data in those tables and your users. Access has excellent interface tools.
You'll be able to automate the processes using VBA. That's an also integral part of Access.
Most likely scenario is that you'll build a "wizard-like" interface using multiple forms, each of which is dedicated to one step in the process. These forms would have controls on them through which data can be manipulated (i.e. entry in a text control or selecting one record from a listbox) and a command button to execute code to perform the desired action.
But going into more specifics would require getting involved in the project itself.
Also, I wonder what you mean by integrating it with SharePoint. It's a fundamentally different environment that may or may not be compatible with what you want to do.
Again, I fear being too negative, but at this point, I'm feeling like you want someone to do the equivalent of helping you build "a house of some sort" and that's a pretty large undertaking.
Jan 06 2020 05:33 AM
Jan 06 2020 06:04 AM
You can use SharePoint Lists as tables in an Access Relational Database Application, yes. And, on the SharePoint side I'm sure there are ways to automate certain actions as Workflows. (I don't have much experience there.)
That said, if the automation happens in SP, and the data is stored in SP lists, the data can be exposed in Access, and that means you can do additional processing from the Access side, using typical Access features and functions.
Again, it's kind of a large project, and potentially fairly challenging. If you can implement it, it ought to be pretty impressive.