I agree the database should be centrally located. If we use Dropbox, the entire database is replicated on each users' PC. There are some issues around two people using it at the same time and an annoying tendency to notify everyone when a change is made but it is workable.
I considered something like Team Viewer and setting up a dedicated (and cheap) PC for people to log into remotely. That would really be the sledgehammer approach though.
The perfect world is to publish the front end on the web, I suspect. I was hoping someone had done that or another solution.
Thanks
On Apr 20, 2015, at 8:51 AM, wrmosca@comcast.net [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:This is all my personal opinion. I'm sure not all would agree.
A database must be centrally accessible for real time data entry. And even scheduled syncing is unreliable because of the lack of primary key that can be used as a foreign key in a related table. That brings us to cloud networking as the only viable solution unless data is locally distinct as in one store's data is unique to it but all stores' data can be brought to a reporting database.Regards,Bill Mosca, Founder - MS_Access_ProfessionalsMicrosoft Office Access MVPMy nothing-to-do-with-Access blog
__._,_.___
Posted by: Jan Hertzsch <jan.hertzsch@gmail.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (3) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar