How can I know whether a multi-user Access database has only the data tables on the network drive?

Question

Multiuser Access db.

Slowness issues.

What do I look for to find out whether it's only the data tables that are on the network shared drive, as opposed to everything (queries, forms, reports etc..)?

I understand having JUST the data tables on the network drive...and the application on each user's PC would help with slowness? How does that work?

Sorry, I'm not IT trained. Please help..

Answer 1

Normally it is the data that is shared and stays on the server. The application (copy of) that manipulates the data is downloaded to a client machine on requesting the application.

When you request a single record it is marked as locked on the server and a copy is sent to your machine. This is done to prevent simultaneous updates. Another user can view but not alter the record you are working with until you have finished and written back the altered record to the server (saved it).



If you think the network is slow the first thing you should ask is if the database is indexed.

Answer 2

When you look at the tables in the database, the linked tables have an arrow beside them.



Because you mention multi-user, I can just about guarantee that the data tables are in a shared network drive.



But, for speed, all of the static tables should be in the front-end MDB, not the linked in network drive, which is called the 'back-end' MDB



Static tables such as ones that resolve a location code to a location description. The locations never change so put that table in the front-end. Or something like the container code for box, skid, single, dozen and the description that goes along with it.



The generic answer to 'how does that work' is that MSAccess was designed to work that way, if it's a multi-user setup.

MSAccess is not slow, I have an application that has a main-data table with 300,000 records and no report takes more than a minute. A query to find a set of records, say for a person, within those 300,000 records will return the set in 11 to 20 seconds. no records found is 11 seconds, 200 records found is 20 seconds.

Answer 3

For openers, the application SHOULD NOT be Access. There are many ways to write programs to access an Access database that are faster than using Access itself as the front end.



If the queries are also on the network drive, it will actually speed things up (stored procedures run faster than external queries).



You need someone trained in both programming and databases. (They're two pretty much separate fields, although there are database programmers.)

Answer 4

before everything, MS get admission to grew to become into no longer likely equipped for use as a multi consumer app, yet modern ameliorations have supposedly stronger it. Secondly, regardless of in case you create an exe for the database, a consumer continues to be going to desire MS get admission to put in on their laptop to run the app. i do no longer recognize that it may additionally be achievable to create an exe that contains the database interior of it (?) usually, an exe could be an utility that pointed to a separate database. If value is a controversy, why no longer seem into an open source answer, like MySQL? Microsoft has taken great pains to ascertain that folk won't be able to use their products with out procuring them - in case you attempt to skirt their deterrents, it is going to easily reason extra issues interior the top. besides - get admission to is an element of place of work, isn't it? I recommend, in case you have Excel or word, you need to have get admission to, so value ought to no longer likely be an argument.