I already have created & run an Access database for around 12 users. I now am looking to create a database that can have at least 30 users. Each one with a unique user ID & password (Using a security file ".mdw") Users log into a front end on a network environment. Now...My question...Is 30 to large of a user base for Access in a network environment??
View RepliesI am not sure how to do this. I am trying to do up a password form where there is a user name and a password. There will only be 5 user names, one being an admin. I seen it in the Running Microsoft Access 2000 book (it's just a reference manual) but could not figure it out.
View 1 Replies View RelatedI recently made a database that we will use to allocate appointments between a team of up to 30 in 2 different sites. I have tested it with 10 people in the same site using it and have had no issues so far.
One of our managers wants to know whether it is likely to cause issues with network usage/congestion. When we introduce it to the other site. I told her it is unlikely, but went to our IT department for their opinion. I got a reply simply stating that Access is not intended for this sort of task, and is only designed to have a couple of people using it at a time.
I'd like a second opinion, because I don't think that answer is even close to correct. I'll describe briefly how it works and what our set up is.
The database has 2 tables, one that stores the details of the clients we call (7 fields), and another that logs each contact attempt (6 field) and ensures no 2 users get the same entry. I have split the database, with the backend saved on one of our networked drives, and the frontend will be distributed in an email. (at present it is just an unsplit database stored on a network drive, but I don't think this will work well when 2 different sites are using it).
I think data throughput will be minimal, but I don't know how I'd go about checking that. Would you expect any issues with this being used by 30 people simultaneously?
I have read through just about every post on this forum related to "Unrecognized Database errors" and have not found a solution to my direct problem.
Stats:
Database is running Access2K on all machines; db is on network location, no sharing issues or permission issues have been identified, no other databases in this network location have had this problem. also, we have tried compact-repair and also have tried re-creating the database and neither have proved successful.
I can open the database just fine if I am the only one opening it. If someone else tries to open it once I have it opened one of the following occurs:
1. Nothing. Hourglass appears for a split second, then nothing happens.
2. Error message "unrecognized database format "mydb.mdb"" appears. If I click OK and both users close the db, it can be opened just fine again by the first user. It doesn't matterwho opens it first, but the second user gets this message.
Any ideas why this is happening?
Thanks!
Currently the system where I work is set up so that everyone has their own front end on the local network. I would like to change this because updating all of them takes a lot of time for me and skill level for users is too low for me to trust them with updating it on there own.
My question is this:
If I were to create a shortcut on everyone's desktop that linked to one front end would this be wise? I can't seem to get a straight answer from anywhere on the internet. I know most places say that it is better to have the actual front end on the staffs computer but that would make my job of keeping the database updated even worse because staff have multiple computers and this isn't my full time job.
If this is okay practice how many users would this be able to sustain? Currently we only have 6 users on the database with there own front end and it works great. I am planning on adding around 10 more users in the future but if needed they could have there own database as they are separate programs.
I have an Access database which has a linked table to a CSV file.Only one user can use this part of the database that links to the CSV - for other users we get the error 3051 - opened exclusively by another user. How can the csv file be a linked table with multiple users ? The query itself is set to no locks.
View 5 Replies View RelatedI've prepared a front end database with forms that allow data to be keyed into linked tables to my main databse.
However, currently the front end database only allows 1 user to do it at 1 time and when another user tries to open the file, an error "The Database Has Been Placed in a State by User on Machine That Prevents It From Being Opened or Locked'
Is there anyway to allow multiple users to use the front end database at the same time?
I have a simple access database that 26 clerks in my office use to enter their weekly tasks. The database is split into a front end and back end, with the back end stored on a shared drive that we all have access to. We have been testing the database for 3 weeks with 5 clerks and no issues. This week is the first week that all 26 have used it, and immediately we encountered a problem.
I think the problem is happening because one of the tables in the database is linked to an excel spreadsheet. When multiple users try to use a dropbox that is linked to this table simultaneously they get an error message. I saved the excel file as a shared file, but this did not correct the problem.
I made a copy of the database before I split it. I know I can fix this if I import the excel spreadsheet into a copy of the database, link this table to the dropboxes, split it again, and redistribute it.
would like to leave the front ends linked to this spreadsheet, because we update it regularly. If not, we will have to have somebody update that particular table in the database intermittently.
How do I change the database for multiple users?
There is no "advanced" option in the options tab.
Good Afternoon,
I have been given an access database system which runs using about 7 access databases, linked tables etc, quite complex. When a new user installs the system from a DVD the user needs to provide a password. This password is filtered to all 7 access databases so they all use the same username and password.
The problem I am having is when the user runs this application again they are prompted for their password. Everytime they click on an option which is another access database they are again asked for their password. I am trying to figure out a way once the user has logged in once on start up no matter which option they select and no matter how many time they select it while the main appliction is running they are not asked for their password. Is this possible or totally outside the scope of Access databases.
I have two separate database files, a front end with all my forms and a back end with all my tables. The backend is stored on a network drive, is there any way of being able to store the frontend on the drive with the backend? Users do not use the actual computer to store information or access files, everything is usually saved on the network drive. I have created a shortcut that launches the front end database in the read only kiosk mode.
View 5 Replies View RelatedTwice a year, a database of mine is accessed and put too use by various staff within a time range of 1 week. the database is on a shared drive and in a location which can be accessed by all.
The staff access the database from different workstations and in some instances at the same time.
This has only led to issues in the database being copied and then confusing staff on what database to click on thus i have 2 databases which i then have to sift through and copy/paste into the correct one.
I want to know the best way i can:
1) Prevent multiple users accessing the database at a time.
2) making a copy of the original and typing into a separate database.
Hi,
I have a database that i created for our tech support team. I have split the database and have given the 3 users each a shortcut. I als e only installed Access Runtime on their machines.
The first user in pilot testing had no issues and we have just added the other 2 users. At first all was well. However, the 2 new users are now having periodic lock ups where they go to enter a new record and the dbase freezes on them. It seems to release itself in a few minutes, but this does not help my productivity.
My original user is still not having any trouble. Does anyone have any ideas of something that perhaps I missed? Everything I have read, suggests that 3 users should not have any trouble using a split dbase.
Is it runtime that may be causing this? I have considered going to full versions if need be, but then I would need to figure out how to lock it down better.
Thanks
Dave
how can i change a database to allow multiple access?
is there a downside to doing this?
eg. if two or more people are trying edit the same feild???
--------------------------------------------------------------------------------
I maintain the Access databases at the hospital that I work at. Last weekend, our server went down. Computer Services got a new server and reworked the networking permissions. However, Access will no longer allow more than one user to open the database at a time. This is a problem because we always have multiple users that need simultaneous access. The default is still "Open Shared" and I checked to ensure that the databases are not being opened exclusively. However, the message that I do get when a second user tries to open the database is:
The table 'MSysAccessObjects' is already opened exclusively by another user, or it is already open through the user interface and cannot be manipulated programmatically. (Error 3008) -
I understand that this message usually comes up when I try to open a table that is already being edited elsewhere. I have the record locks set to "edited record". However, this is a system file, so I am hesitant to make changes in it unless I know exactly what I am doing. This is a problem that we have never had before but for some reason was created after our server went down. I don't know why something changed or if this table is absolutely necessary. I am unsure where to start to solve the problem.
I have an MS Access application for about 40 users. The problem is that the company does not want to have to buy all these licenses and put it on each machine. Also because each person had to bring in their own set of data multiple people cannot be hitting this at once. So they want to know if there is a way to allow the people to use it without having the application on their machine; and thereby saving the money of buying 40 licenses.
View 2 Replies View RelatedHi,
I would like to use an Access database over an Intranet. What are the limitations of doing this? I want multiple individuals to be able to open forms and enter data. I would also want others to be able to run queries and reports on the database. Would I need to upsize to an Oracle database to run with multiple users? Any words of wisdom would be appreciated.
Greetings. When I create an Access database on my company's "secure" server (through a PIX box), I get this message in a dialog box when I try to open the database again: "Open File - Security Warning. Do you want to open this file?" It then gives the file Name, Publisher (unknown publisher), Type (Microsoft Office Access Application), and From (the file path and name). The bottom of the dialog box has this message: "While files from the Internet can be useful, this file type can potentially harm your computer. If you do not trust the source, do not open this software." When I click on the "Open" command button, the file opens just fine.
There are a couple of things going on here:
1) When I open this same database or any other Access database on another of my company's servers that is not protected by a PIX box, I do not get this dialog box.
2) When two users try to access an MS Access database on the "secure" server, the first user will get in, but the second user will not. The second user will not get ANY warning messages -- nothing happens. This occurs if the second user tries to open the database by either double-clicking on a shortcut on the desktop or by double-clicking on the file name in Windows Explorer. Note that the second user CAN access the same file if s/he starts up MS Access from scratch, and then chooses FILE>OPEN from the main menu.
My goal is to be able to let multiple users access the MS Access databases on the secure server by either double-clicking on the shortcut icon or by double-clicking on the file name in Windows Explorer.
I thought perhaps that the "unknown publisher" issue might be part of the problem on the secure server. So I created a certificate using the utility "SELFCERT", went into the database, went into Visual Basic (Ctrl-G), went into TOOLS>DIGITAL SIGNATURE and assigned the digital signature, and re-saved the file. I then exited the file, went back in, and the dialog box still pops up saying the file's publisher is "unknown publisher"! If I go back into Visual Basic, the database is clearly marked as digitially signed by me. I don't know why the initial dialog box is still showing that the file is not digitally signed.
If anyone has any thoughts about these issues (multiple users not being able to access the same Access database, and why my file is saying it is still not digitally signed), I would appreciate your input. FYI, I am on a Windows XP workstation and our company users Windows Servers.
Thanks,
David
I'm having trouble opening up the tools I am developing in Access for multiple users. I split all my databases so the users will only interface with the "Front End" and I just tried saving one as an ACCDE file. I had the ACCDE file open on my machine and asked another person in the office to try opening it (all our files are stored on a network drive, which is already identified as a trusted source).
She got the following error message:
"The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted. Deleting the VBA project removes all code from modules, forms, and reports. You should back up your database before attempting to open the database and delete the VBA project"
How do I fix this? I don't want to publish several Front End Access files since each person in my office will ask me to customize their file and my supervisor wants everyone working off the same file. I thought the point of Access was that multiple users could open the same file and make data modifications. How do I achieve this while retaining all the fun, creative VBA solutions I have developed?
I created an access database for the sole purpose of sharing approved data with my entire company. The end users will view the data in a Form which utilizes several tabs and also gives them the ability to run pre-set queries out of the Form. The Form was created using several queries which were built from tables off of the server.
The tables update every day, as does the information in my Form. The problem I am running into is that it takes about 2 minutes to open the DB (the DB opens directly to the form and all queries run immediately to update), which is annoying to end users and might deter them from actually using the tool. I have tried moving the DB to SharePoint, but that did not work due to the size of many of the tables.
Hi
I'm currently designing a small database which will be distributed to users most probably using the access2007 runtime. I would like to be able to ship the database with a default username and password. Is this possible in acces 2007 ?
If it is possible, how would I go about enabling individual users to change the default username/password and set up a username/password of their choice ?
I have MS Access 2010. I cant remove password because when I open in exclusive mode, file, info, there is no decrypt password option.
View 1 Replies View RelatedHow to validate a MS Access password text box as criterion below?
(i) At least one uppercase
(ii) At least one lowercase
(iii) At least one number
(iv) Password length 8 - 12
--------------------------------------------------------------------------------
I have a dilema on my hands as I can't seem to figure out the best way to accomplish this. I created a database to handle all of our letters for my department in the company. The problem I am having is that we have 26 people who could possible access the database at the same time. The letters are created using a form. (not a problem with multi-users) When someone wants to print the letter the do a search either by "Letter Date", "Provider Name", "Provider Number", or "Group Name". I set it up so either one of these search queries append data into one table called "Letter Report Information" all 38 letters get there data from this 1 table. The problem I am having is that if John and Mary try to pull different/same letters at the same time or while one is viewing their letters the data is getting pushed onto the others Letter.
Example:
Mary goes to print her Welcome letter
John also goes to print his Denial letter at the same time
When John's letters show up.. the Denial letter shows up with his data, but also with Mary's Welcome letter data.
What can I do or what kind of query can i use to avoid this problem as it is becoming a very prominent issue? ::Please Help::
Thanks.
I have a database with three users, only one of whom has editing privileges. As such, I didn't see the need to setup a front end and back end (nor did I know how at the time). Anyway, that's not the issue. The database is saved on a networked computer that all users can access. Unfortunately, when accessing the database in the shared network folder, only the first user can access it. Other users will double click the file and virtually nothing happens.
However, users can instead open Access first, and open the file through the program fine. Why this would be the case and how I can have multiple users open the file from the shared folder?
I know that Access probably permits around 20 or so users to simultaneously access the database before it start to become unfriendly. However, I have a database that would require 200 or so users grabbing around 1,000 rows of data via an Excel ADO connection to the backend tables.
So they would never need to physically go inside the Access database its self, but instead it would garb data by opening an ADO connection to the database > Grabbing the data > Closing the database connection.
Is this okay to do with around 200 users simultaneously querying the database tables via an Excel ADO connection?