Cotswold
New Member
I have seen posts regarding MS Access databases being used remotely. The situiation as I understand it is that Access requires a constant connection and not an intermittent one.
It is therefore susceptable to corruption and I would not myself consider its use except on a PC or a local network. It is not advised that an Access database is used on a local WiFi connection as that will also cause major problems.
Access does not work for most cloud sites because those sites do not support the Server Message Block (SMB) protocol that is the Windows standard protocol for "File and Printer Sharing" operations. No SMB? No Access. The few places that seem to have some type of solution either use a single-user with remote-mirror system, or they use another protocol called Remote Desktop Protocol (RDP).
Additionally, an Access database will bloat and must be regularly compacted and repaired. It will even bloat if simply opened or closed. Any flaky or intermittent network can easily corrupt an Access database, which will result in several or dozens of records being destroyed. Or often subject to 'slip' where the content of one record slips into another.
If the Unique Record Number is used as a link to related data, then that link may well be lost and can never be recovered. Compacting and repair will result in bad records being deleted and the missing unique numbers can never be recovered or replaced. If you cannot relpicate the compact and repair from Access you will have issues.
My advice is that if you are thinking of using an Access database outside of an Access development.........don't.
It is therefore susceptable to corruption and I would not myself consider its use except on a PC or a local network. It is not advised that an Access database is used on a local WiFi connection as that will also cause major problems.
Access does not work for most cloud sites because those sites do not support the Server Message Block (SMB) protocol that is the Windows standard protocol for "File and Printer Sharing" operations. No SMB? No Access. The few places that seem to have some type of solution either use a single-user with remote-mirror system, or they use another protocol called Remote Desktop Protocol (RDP).
Additionally, an Access database will bloat and must be regularly compacted and repaired. It will even bloat if simply opened or closed. Any flaky or intermittent network can easily corrupt an Access database, which will result in several or dozens of records being destroyed. Or often subject to 'slip' where the content of one record slips into another.
If the Unique Record Number is used as a link to related data, then that link may well be lost and can never be recovered. Compacting and repair will result in bad records being deleted and the missing unique numbers can never be recovered or replaced. If you cannot relpicate the compact and repair from Access you will have issues.
My advice is that if you are thinking of using an Access database outside of an Access development.........don't.