How to best distribute Access frontend
My project has a postgresql backend hosted on Amazon Web Services, for which I am developing a frontend in Access. With your help, I'm making good progress, so I started to think about the best way to make the application available to multiple users (think of them as consumers, so no company network or anything like that).
When the weather is good, I like to sit outside and do my coding while smoking a cigar. Since that means working via wifi, the connection sometimes drops and Access restarts. A bit of a nuisance, but manageable. For users, however, this would be unacceptable.
I was planning on streaming the frontend via Amazon Appstream, but the other day, I found out about Access Runtime, so I added that to my list of options. Now I have the following questions:
1. Does anyone have experience with Appstream? Does the "no wifi" principle apply in such a scenario? The user would access the frontend via Amazon, and connect to the backend via Amazon too. My guess is that Amazon has the whole thing cabled up, but there may be some remote technologies involved to make matters more complicated.
2. Is a Runtime application equally susceptible to the wifi-related instability as the full Access application?
3. Am I right in assuming that since each user would be executing their own Runtime package, multiple users at the same time are not an issue (since that is managed on the postgresql backend)?