Split Access Database on RDS Server

Question

Hi all

We have been using a drawing management Acccess database for around 20 years. This is split with front end on clients and backend on our F/P server.

The move to home working means we are looking to relocate all this to a cloud RDS server.

The question is, does it make sense to retain the split front end/back end structure on the remote server, or should the two be merged?

Thanks

Phil

Answer 1

Any multiuser database must be split.

Even single user database benefit from splitting, but it isn't a necessity.

As much as possible, try to keep everything on the server so there is no network involved with the database, obviously there is for the RDS to user but that something complete different.

Answer 2

Thanks Daniel

Will proceed with split option

Phil

Answer 3

You may like to review

https://www.devhut.net/2017/04/09/setting-up-an-ms-access-database/

https://www.devhut.net/2017/04/20/access-best-practices-and-troubleshooting-steps/

Answer 4

perhaps this question is coming from a misunderstanding that in going to RDP that users would be using the same file... that is an understandable yet incorrect assumption...

even in RDP each user must have their own, private, front end file.

one never should have multiple users active in the same front end file as that is bound to corrupt...even though back in the .mdb file-type days it was somewhat common and worked....