Hello everyone! I have been reading the forums for a couple weeks brushing up on my Access skills and finally decided to get some feedback on a project I started working on. I am a project manager but have never managed an Access or a database project. I have a pretty good idea of where I want the project to end up, but I wanted to get some feedback from the fine folks here at AccessForums before I dive in. Forgive me if this gets long-winded.
Scenario: I work for Company "X" and have been tasked with creating a Daily Shipment Report for my client that has multiple facilities that receive shipments. The corporate side of my client wants this report to also show accrual information (ie, how much a shipment should cost and when they can expect to pay it).
Vision: I am imagining a system where the trucking companies can "drop off" their Excel shipment data files into a cloud based drop box, and then have an online front end that can be accessed by both the facilities and the corporate office where they can pull reports.
Phases: I have the project broken up into two phases at the moment: Phase 1 is just the tracking part. Being able to deliver a daily report to facilities showing active shipments and expected delivery date. Phase 2 would be be the cost accrual part for the corporate office. In order to show much a shipment will cost and expected pay date, this phase will bounce shipment data off of an existing accounting database that my company already manages.
Questions:
1) When looking at my "Vision" section above, is there a particular way that I should approach the database building process if the eventual goal is to have it all relatively automated online? Would it be an issue if I go from a scenario where I have the trucking companies email me the data files every day, then I would "scrub" them through the database, and then personally email the report out; to a scenario where it is mostly cloud based as described? Basically, going from manual to auto.
2) Is my "Vision" even possible with Access? I know this question might be more concerned with web/cloud design, but I figured some of you might have an idea or experience.
3) When looking at the "Phases" section, are there any concerns that I can address early on with using the second database in order to avoid rebuilding the database?
Any other suggestions or criticism are welcome! Thank you in advance for any help with my project.