By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
461,997 Members | 489 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 461,997 IT Pros & Developers. It's quick & easy.

How can multiple users access the same query data from different pc's

P: 18
Hi I hope someone can shed some light on this for me

I have been tasked with creating an outbound database system for multiple users. The database will receive a new batch of data on a monthly basis, so I have created an import routine to collect the relevant data that is needed and that works fine. I have created my form that picks up data depending on the criteria from my query.

The problem I am experiencing is when multiple users try accessing the form to complete the data the system just stops.

Could someone please guide me in the right direction on the best way to create my form so multiple users can scroll through each file that is not being used by , 1:Another user 2: ensure multiple users arenít trying to access the same file.

Any help would be truly appreciated, thanks for your time
Nov 10 '10 #1
Share this Question
Share on Google+
1 Reply

P: 83
Look up info on splitting your database into Backend and Frontend. Backend on a server, front end(s) on each client machine.

What is a split database application?

A split database consists of two database files. One database (called the back-end database) contains only the tables and relationships and resides on a network file server. The other database (referred to as the front-end database) contains all the other database objects: queries, forms, reports, macros and modules and resides on each user's computer.

A split database design works well in multiuser environments, and it offers these advantages:

* Performance is improved because the application portion of the database, the user interface, is on the user's local hard disk.
* Network traffic is reduced because only the data travels over the network; all other objects in the database are local.
* Updating your application is easier. You can make design changes to the front-end database, and then distribute the changes to users without changing any of the data in the back-end database.
* In non-runtime environments, users can create their own custom objects, such as queries, forms, or reports, without affecting other users.
Nov 10 '10 #2

Post your reply

Sign in to post your reply or Sign up for a free account.