I'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?
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 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.
Twice 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.
I have a database that logs people in and out. Works great unless the user minimizes the navigation page and clicks the X on the main Access Page. I have to keep the minimize button active on my nav page.
Is it at all possible to disable the main access page for the user? If not, is it at all possible to set a logout macro to the X button on the main page? If not, is it at all possible to set a logout macro to activate on "Quit Access"?
I have been trying to set up a batch file to allow users to copy the latest version of the front end whenever a change is made. The following is the code that I am trying to get to work properly. The first part works fine, the old front end is copied to a folder on the user's desktop as a backup. But I cannot get the copy of the server - the "P" drive, to overwrite the current copy on the user's desktop. Actually I cannot get the code to copy the new front end from the server and install it on the user's desktop. I think the path is correct for I seem to be able to run the new front end from the server.
When I look for the location on my computer, the server locations is listed as:
General (Servernamefiles) (P: ) (there is no space after the P: it seems to result in a smiley face when I type it and try to post it).
for /f "tokens=2-4 delims=/ " %%a in ('date /T') do set year=%%c for /f "tokens=2-4 delims=/ " %%a in ('date /T') do set month=%%a for /f "tokens=2-4 delims=/ " %%a in ('date /T') do set day=%%b set TODAY=%year%-%month%-%day% rem echo %TODAY%
[Code] .....
This code works so I thought that the path was correct rem this works rem start the new DB front end Start P:AccessMainSplitBENewFrontEndDBMain.accdb
But this code does not. echo f | xcopy /f/y/ P:AccessMainSplitBENewFrontEndDBMain.accdb c:UsersUserNameDesktopDBMain.accdb
Neither does this: echo f | xcopy /f/y/ ServerNamefilesP:AccessMainSplitBENewFrontEn dDBMain.accdb c:UsersUserNameDesktopDBMain.accdb
What is the best solution for sharing a front end DB as me having the BE installed at my pc, giving all user the FE and then refreshing table link with BE installed at pc but the problem is that the shared FE becoming slow any option ? as only 5 users using this at a time.
I have a database system into the back end and front end and then created the accde file with the front end file to give this to users on their computer. The back end being placed on a server with a path of type servernamefolder..I have used the Linked Table Manager to point to the tables server name folderfilename.accdb
but in doing this I get a message Windows cannot access servernamefolder..is this to do Network Rights on the server that I don't have permission to access the server and folder.
My question encompasses a front end connected to multiple back ends. It is probably a mundane point, but reading a few articles didn't seem to touch on it.
By this, let me toss out that I am thinking of the personnel where I work when I say 95% have a hard time using email and MS Word, let alone mundane functions like find a file, etc. As such, I have to make my front-ends extremely user friendly.
With that in mind, when developers have multiple back ends, what are thoughts about the best way to relink when required? Even when there are 'more sophisticated' users? Security not an issue or is an issue (inasmuch as can be handled in access)?
Ex: Large corporation with a multitude of user ability. Large database with say 3 different back ends.
I was thinking about keeping a front-end table with each table name and UNC path, hard coding paths to corresponding table names, etc.
Personally I don't have a need for multiple back-ends, but the question came up while reading.
I was looking to see if there was an easy way to create a user front end desktop application for a small access database.I have three users on different computers i would like them to input or amend data within one table of the access database.
I have a split db that has been in use for a few years by about 12 people. The front end is compiled into an accde file.
Ocasionally a user (randomly) might get an error message "Microsoft has detected that this database is in an inconsistent state...." when closing the db and when that happens, a copy of the front end is automatically placed on their desktop.
This front end is always deleted and the original front end continues to work just fine afterwards.
Why are my users getting this error message? Why is the front end automatically copied onto their desktops?
Using Dropbox to host a split database. Ulimately I would like to create a run version for users with the back end held in a drop box directory.
As an unsplit database everything is working fine on dropbox records are saved in a timely manner and great.
Once I split to FE /BE only some records are saved on the BE and some are dropped. Was getting conflicted copies of Back end but manged to stop this happening but the records were noit on either copy.
Gave each user their own FE (on a drop box directory) linking to a BE in a sub directory on the same dropbox.
The key issue is that not all users have access and I don't want them to get into code so want to aim towards a run version.
Is Access set up to handle multiple people entering data into the same table?
We are processing returned mail and enter all the bad addresses into an Access table. The data is simply entered into the bare table. Can two people be doing this at once without the risk of compromising the data?
I wonder if anyone could give me some advice on a problem i have with an access database.
I have designed a database and a data input form to collect data that is input by workers, the problem i have is that only one person can enter a record at a time.
I curently use 2 replicated database's on two seperate computers and run the synchronisation once one person has finished so that all the changes are replicated to the 2 different databases
If there is any other easier way to accomplish this i would be very greatful if anybody can shed some light on the subject.
I created a database and a form on it that i enter myself right now. I am planning on using this database on several PCs with different users. Currently I have this database on the network, but when multiple people try to access it at the same time they cannot access without saving a separate copy or just having read access.
I need to put my Database to work with multiple users.
1- I already have divide the database; 2- I already have made the file accde of the front-end file; 3- I already have put the two files: back-end and front-end on the network server.
My problem now is that if I open a Form to register data the other User can't open the same form to add data. What I must do to work in the same form with multiple user?
I have my database on a server and i want 2 or more users to access that database from different stations at the same time. I am using MS Access 2010, what do i need to do and how do i do it to allow more than one person on my database? The database contains 2 tables - table 1 has 1,450,00 records - table 2 will be populated with some of the records from table 1.Table 2 is empty.3 sub-forms - 1 main form and 1 report (for labels).
Both tables have the same fields, but not all the fields are filled in and each user will be filling in the fields required.Each record is a case, and no more than one user will be assigned to a case.I need at least 2 users working on my database at the same time, i would like to have 4 users working on this database if possible.
The front end has been saved in a accde format and distributed to 20+ users. They have all saved this onto there computers and this is used as an application.The users complete a form on a weekly basis on the application and then save. This then saves into the back end.For some reason I have noticed that a few users submission randomly do not save. For the life of me I cannot understand why.All users have saved them into the back end in the past but every now and then submission for users do not save.
I have designed a split database( with back end and front end), I am just wondering what would be the best way to put a password for both of the back and front end.
So a while back I created a database which I use to keep track of my companies large list of products. It is very simple only 3 tables, 1 query and 1 form. After running into a problem with copying and pasting updates on each computer in the office I decided to split the database on a network drive. This worked for a bit, however I had to add new fields and modify the form, which corrupted the file. Luckily I had a backup before the split.
As far as I could tell all I had to do was modify the backend file and make a new front end. However it seems like it is not as easy as I thought it would be. How do you modify a split database without corrupting the files or using a non-split copy?
I have split my database in Front End och Back End, and both are password protected. The Front End has been converted to ACCDE.
When I try to import to Excel from Front End and/or Back End using database connections I receive a message telling me that I am using an invalid password (even though I use the same password when I encrypt/decrypt FE and BE). I've tried using Access import, ODBC and Microsoft Query. (In some cases I 'm also prompted to set a username, which I do not know which it should be since I haven't set one in my database (except the automatic "admin"))
We have an access Database stored on a server that until now was only ever accessed by the one user. Now more users need to access it at the same time. However when a second user trys to open the database the error message "File Already in use appears". I did not create this database so have no idea how it was set up. I think it may have something to do with being opened up exclusively. Is there anyway around this by creating a short cut or changing any kind of propertties?
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.
