Hello all
I have a "Read only" frontend and Backend as 2 different files on the LAN shared drive.
i have around 50 users logging on to this to view information (No editing allowed by the user).
I read on some of the previous forums that Multiuser frontend does not work that well. I want to know if this is true even if my users are in read only mode??? I have tried with 3 users and it works with out a hitch. i just want to be sure before i roll out this to the entire 50users.
thanks
soni
At work i have a newtwork of computers each with a frontend of my database on it and 1 computer with the backend on it, once there's about 8-10 computers using it, it wont let anymore in it saying something like unable to open, exculsively opened etc. How to i get round this?
If I want to distribute a front end to connect with a MySQL back end ... do I need to set up the system DSN on each workstation that will be using the front end?
I have created a form that I want to share with other people. They will never add or change any of the data - they will only use the form as an information source. I need to be able to access the database to add/change information.
I am trying to develop a multiuser database. I heard that in a multiuser setup the back end should be on the network and front end on the users machines. Could anyone please explain what is these back end front ends and how should I set it up.
And one more (silly) question... Do we really need MS Access to be installed in the users machines in order to do this?
I have a database split with a frontend (FE) and backend (BE). Both reside on our network. I give a copy of the FE to all users. The FE is linked to itself so if I make a change to the network copy the next time a user opens theirs it tells them to close down and it recopies itself. This works really good. The problem we're having is people going and making a shortcut to the networked FE. So WHENEVER they open their FE everyone gets a message saying to close and recopy. The database is about 10mb but for someone across with a slow intranet connection it can take a bit to download. I'm looking ways to prevent users from accessing the networked FE. Can you simply hide it?
Hi! I´ve just made a frontend backend solution with a db i Access2002. I made this because my users 5 persons have a booking system wich they use at tehe same time.
But the db locks all the time... I thougt we would get rid of that problem now.
Is there something I have to check?
I have some lookup tables, can this cause this kind of trouble?
A simple personal database created by me is to be deployed on a home network having two PCs. I did splitting to FE and BE. The BE shows only tables. I would like to have the guidance of experts in this forum for the following: 1. Whether BE to be copied first in the host PC? 2. FE to be copied in the other PC? 3. After copying the Access DB how to link FE and BE between the two PCs? 4. Whether data entry, edit, search etc. possible from both the PCs? 5. If I test with dummy records, how do I delete dummy records, from BE or FE? Shall be grateful for help.
I am evaluating a program for the use of a customer. It's a VB frontend attached to an Access database.
The backend has no relationships. No table in the backend even has a primary key.
My question: Is this scenario acceptable in any way?
I tend to think not, but am unsure whether the design of the frontend application establishes relationships "on the fly". Even if so, the fact that there are no primary keys makes me think I should dismiss this application out of hand.
I am very good at excel and can program macros. I am being asked to build something in access for my company, or at least manage a build. So here is my question... If we build it without both a front and back end, is it easier to take what you have and switch it to a front and back end? Also, when and why is it better?
If I would have a backend table with the data kept in tables and a frontend database with forms and reports and queries etc. and linked tables to the backend db, what would be the right way to secure both.
In my situation I have salary information in some of the tables, which should not be wide open to the holy world. I also need to restrict the access of some queries and forms in the frontend database to different users. That means I need to set up a secured frontend database with different usergroups having different object permissions. So in that frontend database the Users Group and the Admin User do not have any permissions any more. Thats why I created a shortcut where I kept the database and workgroup information in the target. Every user needs to open the database via the shortcut.
Unfortunately I was not able to secure both the backend and the frontend database, because the linked tables in the frontend db are only pointing to a database not to a shortcut. Because the backend database is secured as well (no permission to Admin and Users any more) it can't be opened directly - only by shortcut.
Am I right that there is obviously no possibility to have a secured backend and frontend db via the Jet database engine and Access?
I hope somebody can answer my questions. At least I know that I can't do anything else and I did not something wrong ;)
Wondering if anyone had tried this yet, and if so, encountered any problems. I have a few existing DB's in the office. Split with backend on server in mdb format. I am now using both 2003 and 2007... BUT.. Now that the runtime is out I would like to make my future updates in 2007. So the question is... Has anyone used a 2007 file format frontend with a 2000 to 2003 file format backend? I understand that the new field properties wouldn't be available in the mdb backend, but besides that, would they still link properly?Thanks
I created a database a few years ago and it has been working well. This database is split.
Recently I started to update the front end based on user feedback and I am adding some queries.
I am noticing that sometimes I try to create a new query and Access tells me that the tables that are involved in the query are not related. Sure enough if I check in the front end, the table relationships are not the same as those in the back end and while the table relationships I need exist in the back end, they do not in the front end.
While the relationships were initially created in the unsplit database, it is possible that I added some of them later during past development/updating processes when the database was already split. This is the only reason I can think of for them to be different.
When I add a relationship in the back end (new table or bug fix) do I also need to add it to the front end if the database is split? if not, why would they be different? What kind of issues can this create?
I have a backend-database on a network disk shared by 6 users. All users have a frontend client wich they use to administer the datebase. Everything in the frontend looks ok and they can query the latest data. However if I open up the backend database tables nothing has been updated since the middle of december. If i make a copy of the backend I can open it up and create new posts with ID-numbers that has already been taken by the frontend.
Ofcourse I have doublechecked that the clients are connected to the right backend file (there's only on backend file in the directory).
I was looking for a great way to link and relink BackEnd to FrontEnd and I sort of found it. Bob larson build a great extensive tool to autoupdate backend en master frontend. You can find his great post here: http://www.access-programmers.co.uk/forums/showthread.php?t=111132&highlight=back+end
Here is my problem or wish is more appropriate.
I just want to relink the backend and if the backend isnt found I want to select it using the filedialog.
If I have an MS Access frontend that connects to an MS Access backend, is there a way to hide/permission block the pathway to the backend's folder but still allow access via the frontend db?
Right now I can't dedicate a server to a more "secure" form of DB or anything like that so I'm stuck with MS Access for now. I just don't want someone looking at, say, a link table path and then navigating to that folder and getting access to backend information.
Will like to check, i have a access database which can be open up by a few users.
How can i only allow the first user who open up the database to read and write the database and the follow users who open up the access have only read access?
I've seen different log in forms and tips on multi-user use but can't seem to find info on the following...
We have 6 people at work and I'd like to assign which user updated a form or created a new record...this would be particularly useful on the sales part of the database to track who made a call to a particular customer...
I have a multi user database in Access 2000 that is on a server. The individual users have shortcuts pointing towards the server instance. One user and one user only when opening the shortcut gets the error "you do not have exclusive rights to the database" .
All other users can enter the database with no error box. I have checked the advanced setting under options and they are correct. Ironically if you go to start and open access then navigate to the database shortcut. It opens with no error.
i have my database split (backend and frontend) - both are residing on the server in different folders...users can't have it on their desktop since we're running on a Citrix server and each user only has a thin client.
Now currently I've got 3 users to the system. 2 users can use the system simultaneously without any problems...however the other user loads the front end but the backend data (bookings, despatches, etc) simply does not load - cannot access any data..
On a webserver certian files are stored above the root directory. Therefor the user of the website can never access those files directly. But he is utlizing that file.
For example: We use Hotmail to see our mails. but we never download the complete database.
So is there a method that we can secure the backend using roaming profiles or something else so the user has a link to the backend but cant directly access the backend.
I have read a lot about if multiple users want to share an MDB, they have to create BE and FE and split the database.
I understand having to do that if all those users want to write to the MDB simultaneously.
I have a situation where one person will do data entry (write access), and two other users will just want to view and perhaps just search the database (read).
If only one person is writing at any time, do I have to do all that splitting and FE/BE configuration?
I plan to create a multi-user application on access 2000. There would be more than 20 users simultaneously logging in the database. The database would be kept in Server with high config. The users would work on the database (server) from their workstations. Forms/Queries/Reports ... are in the workstation (client). The database may growup to 70 MB every 3 months. The application will run on the database for 3 months which will be replaced with a new one after that period. Is it a good plan to do so on Access 2000. Am worried about the network traffic. Will the users face it as a very slow application ???
