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'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 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
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 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.
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.
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??
I 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 split my db last week and put both front end and back end files in a shared network folder. I backup the db every day to a different folder on the network server and also to my laptop. I usually backup right after a form update so that the latest version of the form is available to users who want to update their local copy of the front end. I've been sending email alerts to the users.
My question is this: What is the best way to (1) make sure my backup updates the front end on the network server and (2) how can I automatically alert users to update to the latest version of the front end?
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 created a switchboard 'front page' through which I hope for users to access the forms for inputting data.
Within this front page I have an 'enter' button - successfully created - everything.
However, I am unclear as to how you activate this, or any other button. I have linked it to the appropriate form and stated the action I want it to undertake, but nothing is happening.
What further instructions do I need to provide ...and where?!
I want to create a form that allows users to update multiple fields for multiple assets. Below is what I came up with:
Ideally, I'd like the subform to be filled in by having the user select multiple Assets from the S/N combobox field which would then auto-populate the "Type" field. Then they would fill out the appropriate fields they want edited in the top part of the form. They hit save and magic happens. This would also be nice because only assets they want edited would be displayed (easier on the eyes) and no distinguishing would be necessary. To do it this way, I know I would need to use a temp table but I wanna avoid using temp tables.
I know I can do this by adding a Yes/No field in the "Asset" table, setting the "Asset" table as the subform's recordsource, and then putting a checkbox in the subform and allowing them to check the assets that they want to edit (which would also allow me to sort it instantly so that checked Assets are at the top of the datasheet for easy viewing), but I would like to know if there's a way of accomplishing this without the use of checkboxes.
I know I could also use a listbox and that allows them to multi-select items, but I'm not sure if that allows me to group all selected items at the top of the listbox for easy viewing of selected items. Plus it would involve a lot of scrolling (there are over 2k assets).
I have just delivered my front end to the user. I have incorpoated a splash screen which uses the timer event and then a sign-in form opens. Trouble is, when the user opens the FE it just sits there on the splash screen. The Access security won't let the above process run because it stops all VBA until the user shift-starts and clicks the 'allow' button. After that it all works fine until I deliver an updated version and it all starts again. All using A2010. what I need to do to avoid the user having to shift-start?
I am in the process of updating a database to 2010 (.accdb) and cannot get past a problem. We are using Access 2010.
I updated the back end data to .accdb with no problem. I can't link the front end to that data without updating the front end to .accdb as well. There are no tables in the front end.
I try to update the front end to /accdb and I get the error message 'You are trying to convert an encoded database. Decode the database, then try again.'
How do I decode the database? I tried setting a password and then unsetting it, but that made no difference. I have not previously encoded the database.
can't finish the update to .accdb data. The alternative is to stay with 2003 MDB data. Is that a bad thing?
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'm trying to move a couple tables into the Front End of an Access 2010 database because the drop downs take awhile to load. We have horrible servers at work.
I can get some of them to convert to local table but naturally the ones I really need won't. The only table I want to remain in my backend is "project log data final". I don't even get an error message it just doesn't do it. Why would it not let me convert some to a local table. Does it have anything to do with relationships?
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.
I have (on a company network) a FrontEnd .accde and a backend .accdb - currently ~ 10 users (some over wifi - slow!)The FrontEnd is becoming a rather large file ~ 10 MB and is also becoming slower.I am looking to separate this in to 3 FrontEnd files as to simplify and to lessen the file sizes etc.
My question is - are there any issues around a 3 x FrontEnd databases all connecting to 1 x backend database holding all the tables - over a network?
I just split my DB into a front end and a back end. I only want the users to have access to 2 forms in the DB because the form already has buttons that link to all other forms and reports needed. How do I customize the front end view so that they only see these 2 forms?
I have recently asked about being able to use my table system online. i have just thought. what about creating a front end that works online. still have the front end on the desktop and the table system on the desktop but have both of them connecting to the one table system.
Simply put, I have a front end that does a bunch of file moving and if it encounters an error and stops processing (which is intentional) I am the only that can login to the machine and fix it.
Is there any way to run it that would allow others to login on their own user profile, solution the problem, and start the processing again or am I stuck to a "per profile" instance?
When converting the Front End of my database to an MDE, Access just hangs and says (Not Responding). I've left it our an hour and there's no sign of stirring.The Back End converts in just a second or so.
