We are using a MS Access database (front-end and back-end databases) for the time being. The front-end DB is used by multiple users, who access the same back-end DB.
In a LAN network it works brilliant by using typical Windows clients and a Windows file server. The DB drive is mapped as usual and the back-end DB is accessed via the âMS Accessâ access manager.
This approach doesnât work by using a) the Nextcloud client or b) some command-lines:
a) Iâm aware Nextcloud client has typically a local copy on a Windows client and cannot synchronize data with the foreign server where the back-end DB resides on.
b) here Iâm using two command-lines such as:
net use "%DRIVE%" "%WEBDAV_HOST%" /User:"%WEBDAV_USER%" "%WEBDAV_PASSWORD%" /persistent:no
and to convince MS Access to accept a HTTPS connection string
mklink /d %SHARE_DRIVE% %DRIVE%
So far so good, this work fine for a single user, but not for a multi user approach, because the record lock information is not transferred to the Back-end DB from front-end side.
Question:
- Is this in general not possible with Nextcloud?
- Or do I bark the wrong tree and I should use another back-end database type like MySQL instead?
Environment:
Nextcloud Server Version: 28.0.7 Enterprise
I would say that it is generally not a good idea to access databases via mounted remote network drives. WebDAV makes the whole thing even worse. Server Message Block (SMB) is better than WebDAV.
It is best if the application and database are close together. Unfortunately, I donât know your application. A LAMP software bundle would probably be far better. Why does the client need direct access to the database? Maybe thatâs where the error lies.
Well, the MS Access DB and not developed as a web application. It is a relict from the team and managed by one of the team members.
My personal experience was to go with AWS or Azure instead.
I already mentioned in the team to go this way and bite the bullet. Your advice underlines this approach.
Thanks for your valuable feedback.
Well. You used to use a real remote network protocol with SMB. Neither Microsoft Azure / Microsoft 365 nor Nextcloud really offers you that. You now communicate via HTTPS with all the advantages, but also disadvantages in your case. It may feel even better with the Microsoft solution. But this is also a step backwards compared to SMB.
Your outdated application is not made for modern communications. Software development has progressed - unfortunately to your disadvantage. You have lost out with every new solution.