Safe Number Of Users On A LAN In FE/BE Environment
Jan 10, 2008
Hi
Can anyone give me some ammo to tell me boss what a safe number of users of an access database is. It is a well built database that runs quickly and effiecently but I need to know at what point this will be put at risk.
100 users? 200+?
I am running the database a FE/BE with the client sitting on each users pc and the BE sitting on a server. The network is 10/100.
I currently have the following setup for my database which is working as desired when only being used by one user at a time:
Front end: Access 2010 database in Citrix Back end: SharePoint List
The problem is that only one user can open the Access Database at a time since this action locks the database for other potential users. The locking occurs due to this link to the back end SharePoint list.
allow multiple users to update the SharePoint list through the access database at the same time?
I am trying to find out how to integrate ms access with source safe and also the cost of source safe. The microsoft website does not give me information on the cost or even how to buy source safe. Can any one help me??
In a Related Tables, you need to enter a FK to link to the other table.You either key in the FG from memory..The standard procedure is to design the field as combo box AND use SQL to select the field that will input the ID of the other table. So, if you want to input foreign key 3 , the combo box will display what 3 is then when you selected Access will insert 3 for you.
My question is since I can later on, edit the table and change the the value to another value, and mess the whole thing up!!! HOW can I lock my first choice so it will stay unedited ? My second question is: Is this the only way to input the FK if you do not remember the exact ID number or there are thousands of records in the related table.?
If I place the program on a server, how can I tell which users are using the program? Also, is it possible for me to kick someone off the program without going to their computer?
I would like to limit the number of users connected to a shared database. Each user opens a database as the default 'Admin' user. Does anyone know how to do that without user authentication? What event occurs when a user opens the database? How to supervise the ldb file that manages shared usage? I suppose it should be something with the Workspace object.
During a promotion we are running the customers are only allowed 3 entries into the system per day but the users are occasionally putting some customers in more than that. I could use some kind of function that limits the number of times the account number can be put in on a given date. (Or daily)
I have the following text boxes: ID, Customer first name, customer last name, account number, date, time.
During a promotion we are running the customers are only allowed 3 entries into the system per day but the users are occasionally putting some customers in more than that. I could use some kind of function that limits the number of times the account number can be put in on a given date. (Or daily)
I have the following text boxes: ID, Customer first name, customer last name, account number, date, time.
We have a database that is split. Every user has their own front end (installed via a .bat file so that the users always have a local copy of the most recent version), linked to a shared back end on a server. This seems stable and functional for us so far.
However, because our users are geographically separated, I don't actually know how many folks are using the database. I know the folks who contact me, but everyone in our company could use it if they wanted to.
For requesting funding, guiding future development, etc., I need to get some metrics:
Total number of unique users Avg uses per day
Total number of simultaneous users (daily, weekly, and monthly maxes and mins)
What is the best way to get this info? Write user info and a timestamp to a table each time a front end is launched? Are there tools for monitoring this sort of information?
I am having some major problems so i thought i would ask you guys out there for some help because i am starting to bang my head against a brick wall.
I have a simple database, well i have 3 but the problem is only occuring on 1. each of these databases sit in a shared folder on the company network. I am trying to allow multiple users access this database but every time a second user tries to open the database they are unable to get access and receive this message
The table 'MSysAccessObjects' is already open exclusively by another user
However i have set the default open mode to be shared.
can anyone help as i really need this database to open in shared mode.
Hi guys, i read about this before but it did not work.
i am trying to hide the access environment but i couldnt. i read in this forum that if i have a bmp with then same name than the db, the picture would replace the access environment. I have done this but the only thing that i achieved was to see the picter before access env. comes and then it desapears and the access env. shows up.
I was wondering if anyone would be able to help me here.
I have a database created in Access .MDB. It operates allright on my machine. However, since this database is done for my client, i have a problem i need to ask for help.
My client doesn't have microsoft office software installed on their machine. So when i passed the database onto them, they somehow can only run it in the run-time environment. Don't ask, I'm not sure about this at all. Anyway, They came back to me saying that they have got a run-time error message in the middle of running the database.
On my end, it's hard for me to debug since it works fine here. I was wondering if anyone would be able to tell me how i could have this database run in the run-time environment as my clients do. This way, i could debug the problem.
Is it possible for me to run my access database in run-time environment? how do i do that?
I need to allow my MDB to have 15 users accessing at the same time. They will be updating different parts of the same table using different forms. The system will also do an automatic update from another system in 15 mins interval.
Is it possible? If so, how do I configure my access database?
Has anyone deployed or is anyone using an access database in a shared drive environment over a network? If so, how is the databases performance and what kind of problems/headaches do you encounter in this environment? Thanks.
The database has to be handled by a web service and/or a web appliction making the comma delimited option occupy more server time breaking down the string into usable user_ID's. But (and this is probably my actual problem) if i was to impliment my second idea, I'm not sure what I should make the tables primary key or the best way to relate it to the main user table.
My initial thought is to just have a, technicaly useless, ID be the primary key and impliment a one(User) to many(friends entries) relationship... but im a bit of an access n00b so thought i better come ask for some advice.
Hi, Im working on a database that has to be shared by 3 or 4 users. In on of the actions that the database performs, it has to delete records from a table first. When sharing the database, it always asks the users (using access viewer) whether 'they are sure that the want to delete the records'. Does this always happen? And why? How can I get rid of it? Would it matter if I change it from a table to a query?
Hi! I have constructed a database in Aceess 2002 that four persons or more are going to work with. The users have there own computers in the same network. And they are going to work in the database at the same time the database is placed on a shared drive in the network. They must have the possibility to work in the same bookingformular. Is there something that I have to think about so that everything works allright? I mean in the multiuser environment. I had a lot of problems when rhe same people worked with an Access 97 database, But I hope that Access 2002 is better for multiusers. Is that correct?
hi, am trying to create an application for a company that has a small call-center (strength 20). the db is in the central server and each caller sits with frontend on their computer. the central DB is shared on the network which these 20 PCs are accessing.
The frontend: 1 Form only which is based on a query that displays records. Form Lock property: Edited Records Query Property: Edited Records
As the telecaller starts calling the customer looking at the records, they are not able to edit certain records as the respective record is locked by MS-Access when am sure that no other telecaller has opened the particular record.
I am currently using the SetValue function from within a macro to set the value of one text box to the value of another. It works fine under full version but when I use it under Runtime which is where the final application will be run from, it brings up the Halt box and will not continue the macro. Does anyone know what can/cannot be done within Runtime. Is it just the same as A full version but without Design functions or are some other functions removed. I am painstakingly having to go through all the vba code that I wrote in full version and I am having to change so many things in order for it to work with Runtime. This is a real pain the backside! Any thoughts would be huuuugely appreciated.
I am using MS Access 2000 in a Windows Terminal Server 2003 Environment and the performance is incredibly slower than running the same job on a Stand Alone CPU with Access 2003.
Any idea? Access 2000 is running slower on a TServer? May the Access version difference explain the difference?
I've gotten to a point with my database where I have split it into front and back ends, and then made a copy so that I have a test version and a live version. I have users in live who've started keying data, and I'm working on forms and tables in test that I then copy to live as they are completed. Up to now, I've been just copying the individual item in test, and then pasting it over the version that exists in live (example: I made some changes to a form in test, copied that form, and then pasted over the version of the form that was in live).
Where it gets tricky is that I am also in the process of designing and insurance underwriting feature that's going to be a part of this application. I've set up all the tables in test, and now that I'm working on setting up the relationships, I'm wondering how I'm supposed to copy the relationship setup into live. Am I supposed to be copying the entire front-end from test when I have changes, and replacing the existing "live" front end with it? And if I do that, will I have to edit it every time to keep the new live front end from sending data keyed into it to my test version (had that happen when I initially split it)?
I'm in the process of rolling out a new database that will require some data entry from approximately 35 users.
I have been told that database corruption WILL (not might) occur if more than one user is in the database at a time, which I find hard to believe. I was told that if multiple users who have different permissions levels are in the DB at the same time, this will cause corruption.
Has anyone heard anything like this?
Also, there will only be one or two forms that my users will be using for data entry. The rest is report running. If I set the value Record Locks on the form to EDITED RECORD, will this prevent corruption?
Any input you could provide is very much appreciated. I haven't been able to find any info specific to this issue.