Forum Discussion
Solved
Shared Access Database Launched From Teams
I am always looking for was to start using Teams for more than a messenger program. Now after Ignite, I am determined more than ever to start now. One of our engineers found this Access Program ...
- I know this is not what you want to hear but Access DB will never work very well over WAN or internet. It was barely usable on a LAN with high speed ethernet on mapped drives. Access DB is very susceptible to corruption and row locking problems when in multi-user scenario. You may get it to work by mapping drives using WEBDAV to the Teams location or by copying to a single users OneDrive and creating shares but trust me it will never be stable and offer the performance you desire. You may be better served to spend the time using the New Lists App in a Team tab or migrating the DB to a SQL server instance in a small Azure subscription and maybe use the Access DB for Forms and Query front end from each workstation and link to the Azure SQL.
I am not condoning this but, if you really wanted to try and use Access within Teams.
All the users must be members of the Team and Channel that you want to use. Unless you are going to break permissions of the SP Library (which is not recommended).
Upload the Access DB into one of the Channel Files area.
Then use the Sync feature of the Files tab to sync.
Open the Access DB from the Synced location on the local computer.
Cross your fingers and hope that a WAN or LAN issue doesn't lock or corrupt the DB.
I am also interested in this. I want to create a database and share the content of tables with colleagues. Downloading which in the case of Access happens, is not what I want.
Does anyone have a workable scenario? Maybe something setup with one of the new "Powerapps"?
Tips and suggestions are greatly appreciated
Does anyone have a workable scenario? Maybe something setup with one of the new "Powerapps"?
Tips and suggestions are greatly appreciated