How good is it for over-the-network, and how to open with an exclusive right?

[stingray]

Hello.


I just made a DB that is about 1MB. 2 forms and 2 reports. Tables have 50 records total. 5 new records per month. So it is very small and I did not split it into front end and back end.

1. All Users have Access Runtime. Is there a way to open a shortcut to a LAN location, with an exclusive right? Os there a switch that I can add to Shortcut Property?
2. I really don't need to worry about corruption? since DB is so small, and concurrent user may be at most 3? I understand ACCESS is not good at being shared over network, but maybe it is strong enough. A lot of people use it over network anyway!

Thank you!

[Welshgasman]

DB needs to be split.
Each user needs their own FE.

Otherwise expect corruption.
Access is relatively fine over a network. I never had any problems with mine.

[moke123]

I understand ACCESS is not good at being shared over network

Access is fine over a LAN, not so much over wireless or the internet.

[CJ_London]

I understand ACCESS is not good at being shared over network, but maybe it is strong enough. A lot of people use it over network anyway!

sounds like you have been informed by the uninformed.

unless this is a temporary app used by one person and you are not worried about possibly losing it, you should always split the app into back end (tables) and front end (everything else).

The backend should be located on a server (not onedrive or equivalent ) and each user has their own copy of the front in their local machine and connected to the back end via a LAN. The front end should have the same design principles as a web site in terms of how it interacts with the data - minimising the amount of data moved across the network.

wireless can be an issue- more reliable these days but still prone to the occasional loss of connection which if it occurs at a critical moment - for example when updating/appending data can result in corruption.

so perfectly good at being shared over a network- providing you do it right.

[ArviLaanemets]

... and each user has their own copy of the front in their local machine and connected to the back end via a LAN.

Or on resource in same LAN where Back-end is stored;
Or in user's profile in Terminal Server in same LAN where Back-end is stored.

Those locations are obligatory, when the users needs to work with database using remote connection.

[CJ_London]

Or on resource in same LAN where Back-end is stored;

Not clear what the difference is between the two statements but simple having multiple copies of the FE on the server (one for each user) although works,is not efficient as everything has to come across the network, FE included

with terminal server, the user is logging into a user profile on the server so everything happens there - the only thing coming across the network is screen refreshes. To my mind its the most efficient and secure way of using access for multiple users in multiple locations - but comes at a cost

[ArviLaanemets]

Not clear what the difference is between the two statements but simple having multiple copies of the FE on the server (one for each user) although works,is not efficient as everything has to come across the network, FE included

Simply I listed all possible choices.

I myself would prefer:
In case the user works both from computer in LAN, and remotely - the front-end on network resource on LAN;
In case users profiles (i.e. My Documents folder included) are on OneDrive - the front-end on network resource on LAN (or on Terminal Server profile in case user works only remotely);
And in case there are multiple Terminal Servers on same IP used in LAN, it would be probably best to avoid keeping front-ends on TS user profiles too. In my last firm before my pension, it was the case (and the Network Management was outsourced) - so at same moment a new TS was added, and users didn't find their front-ends there.

[Micron]

Os there a switch that I can add to Shortcut Property?

In case this is still relevant after the answers given, yes. I'd suggest using cmd (command) switch and use command function in your db code. This uses the argument portion of the switch, so you can detect that the db was opened via the shortcut or not. At least that's what I assume you're asking for.

[stingray]

OP here.
Thank you everyone for your comments. Since the consensus is that ACCESS in LAN is pretty reliable, I am not going to worry about exclusive right to use it.
I will split the database as well, though very small. Gracias!

[Welshgasman]

OP here.
Thank you everyone for your comments. Since the consensus is that ACCESS in LAN is pretty reliable, I am not going to worry about exclusive right to use it.
I will split the database as well, though very small. Gracias!

Always best to keep the data and code separate. If yiour code mucks up the DB in any way, the data is safe.
Take plenty of backups, even during the day. I constructed a backup routine that was just a couple of clicks away. So easy to use. Make it difficult to backup and you will rarely do it.