I was just wondering how many users Access would be able to handle on a split frontend and backend database? The backend will be on a network drive and the frontend will be installed on each workstation. My database is pretty simple with no relationships if that matters. Also using Win7 and some users will have Office 2010 and others will have 2013.
Alright, so my pride and joy and departmental savior database has been fully implemented and people are so pleased with it that they *all* want to use it at the same time. Initially, I made it custom for three peoples' UI preferences, but since it's such an intuitive design, other staff now feel comfortable using it instead of passing the work down the line to the one person who knows how to use that "newfangled thing".
A couple years ago, I used FMPro and allowing for multiple users at once was an annoyingly complicated process dealing with permissions and rights and accounts and passwords and yadda yadda. Is it any easier to set up in Access? Does anything special even need to be done to allow for multiple simultaneous users?
I have a db on a network drive and the performance is terrible, it runs fine on my local machine. How can I make it run better? The db is only 2 megs so I figured it would be ok, but since my forms have numerous queries within them, performance stinks.
I was using the database when there was a network error and I had to close it. When I tried to reopen it I got the error message: Record(s) cannot be read; no read permission on 'MSysAccessObjects'. I logged off the PC and logged back on various others, but keep getting the same message. Can anyone tell me if this is terminal or is there a way around it. I do have a backup, but it's a few days old and a lot of work will need re-entering' so any help would be appreciated!!
Does anyone have any experience with placing a multi-user back-end access database on one of these inexpensive "external network hard drives"?
I have a situation where I'd like to share my database with multiple users, but the corporate IM rats have pretty much eliminated all means of allowing us lowly employees of doing that with their network. We have no file server. We do have sharepoint services, but we only have Access 2000, which as far as I know is not capable of exploiting the sharepoint/xml back-end database features. Also, no one in the office here can share a directory on their workstation because they won't grant us administrator priveledges.
So thats how I came upon the idea of buying or creating cheap (<$250 USD) wireless network hard-drive on which to put the back-end. I'm mainly interested in knowing if it will work, and that the performance isn't going to be absolutely pathetic. I'm only looking at having 3 or 4 users at any one time, and the entire database will only house a couple thousand records.
I have an ACCESS 2003 application with front end in the local machine and backend on the shared network drive. I mapped this drive to E: in my computer and all my linked tables show the E:folernameDatabasename.mdb as the source.
When I install this application in an other computer where they have mapped the same drive to F: , I am getting error that says "E:foldernameDatabasename.mdb" not found. How can use absolute network drive(like \cscrd eamfoldernamedatabasename.mdb) name to link the tables?
I am attempting to link a table in one database to another database using the server name designation (ie.//2sxfprinff01Group) instead of the mapped network name (ie. G:). I tried relinking using the Access Link Manager. Right click on the linked table. But it does not let you edit the link.
Access 2007 does not allow this and reverts links to the G: drive. There are situations where the the IT department have set the mappings to this shared location as an H: for some of the employees. In those cases, the employee gets an error message telling them that Access cannot locate the G: drive.
An obvious solution is to get the employees remapped to the G: drive. However, one would think that MS would have allowed for mapping to the designated location and not an alias.
Here are some background . My company got a access file in a network drive.The data entry simply open the file in the network drive.But once the data has increased (~400mb) sudddendly,all process slow down. Like search , using report etc.Is there any method to imporive the situation?Some guys suggest me to copy the data file to the desktop and sync them.Can it it work?IF works,how to do that?
I have been searching and found a few great threads about checking users but the codes there were incomplete. Is there a way to effectively log a user's name & computer name when they open your database and also log when they close/exit your database. Without them noticing but just for your own personal security incase something happens and you would like to know who all was actually working in/on the database at that specific time?
Or just something that will show me who is in the database so I dont' have to keep seeing network333 something has it open.
Thanking you all in advance, and I know I am a P.I.T.A.!
I will have around 10 simultaneous users of a database. Each will probably keep it open all day and subject it to fairly light use.
I will split it into front and back ends, the be going into a network folder.
Where would you recommend I put the fe?
Should I put one fe in the same folder and let them all use it at the same time? I presume that would be faster than giving them all a copy of the front end to use on their local hard drives?
I have considered adding the facility on the fe to allow user-definable defaults, like the user's name, to speed things up for them but i assume that will only work if they each have their own fe and not sure if it's worth the hassle if it's faster to have one fe in the same network folder as the back end.
I need to make sure that all users on the network can access a specific network drive folder.
Most users don't have a problem but some users have the network drive mapped differently so when running the feature required their system can't find the file at that specified location.
I have the location of the files hard wired into the VBA code.
E.g. Z:INVDATACOMPANIESCompanyAASSETS Pty LtdPrecedents 2015STAGE 3A - COLLS-DEMS
The location is outside of the project address.
I need to be able to make sure the address of the folder is the same for all users.
My database is used by a few users on a shared drive in "read-only" mode so they can't change any data.I set a scheduled task to copy an updated version of the database (which I edit) every morning.
The problem is that when the users forget to close the database file I can't overwrite it.For this purpose I wrote a small code that quits the application at 00:00 using Application.Quit.The code WORKS when I test it on my computer, but every morning when I try to open the file I see that it is opened by another user since I also open it as "read-only" - meaning the code didn't work...getting the code to work properly OR get a better solution to be able to overwrite the file even though it's opened by other users.
My workaround was to temporarily map the URL to a vacant drive letter on the local machine, then copy the file over, then drop the mapped drive again. A bit clunky but doesn't incorporate much of a delay and this download only has to happen once per day.
The good news is, the file download / copy now works every time. The bad news is that removing the temporarily mapped drive after the copy has taken place, doesn't and I can't figure out why.
Here are the functions I use to map / unmap the drive :
Code:
Option Compare Database Option Explicit
Private Const RESOURCETYPE_ANY = &H0& Private Const CONNECT_UPDATE_PROFILE = &H1& Private Const RESOURCE_CONNECTED As Long = &H1&
[Code] .....
I have separate functions to check existing drive mappings on the local machine and thus determine an appropriate vacant letter to use for the temporary mapping - they work fine.
Unfortunately the UnMapDrive function returns False (even though I switch the active drive to C: and force the connection to be cancelled with the fForce flag) So the mapping always remains on the users profile.
I don't want to permanently map drives on the users' profiles, just briefly for the purposes of this daily file download.
I have designed a database which I intend to split for multi-users to access from one front end icon on a shared folder at work. I have designed a form bound to cmr record table and on it a subform to another table where cmrs activities will be saved. The form has buttons to and blank controls.
User can create a new activity entry by typing into the blank controls and pressing the save button which saves to the activity table. the edit button extracts a selected records details (selected on the subform) from the activity table and populates the blank field for a user to edit and then hit save to save changes. The delete button deletes a selected record from the activity table. I intend to have multi-users either accessing, viewing and a possibly editing the same customer at the same time. The simultaneous viewing is essential but the simultaneous editing, though not desired is inevitably going to occur.
What I would like to know is:
1. Can you lock an individual record in a table or does the whole table have to be locked. E.g If Colleague 1 is editing Cmr A's record in Table1 can he lock it so Colleague 2 can view and edit Cmr B's record in Table1
2.Can Colleague 1 access/read Cmr A's record in Table1 to retrieve details toe the form controls if Colleague 2 is viewing or editing Cmr A's record in Table1
3. If record lock is possible, how can I initiate it in my example code below.Edit activity record Code
Code: Private Sub Edit_A_Click() 'Get Data to text box control With Me.R_P_Data_P_Subfrm.Form Me.txtrID = !rID Me.txtrID.Tag = !rID Me.txtrefNo = !refNo Me.cmbrpc = !rPC
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.
I have an exrternal shared drive "E:"where I put my be files (which are constantly accessed by users with fe's from different terminals). Everytime I reboot the computer that I am working on (where the external drive is), I have to set up the permissions of the shared drive "E:" all over again, otherwise other computers have no access to E. Is there a way that I could fix this and not having to set permissions every time I reboot my computer? For some reason, the permissions are lost.
Does anyone know if Access has a built-in control that allows users to scan the directory structure of their PC? Similar to the DriveListBox and DirListBox controls in VB6? If so, how might I get access to it?
Is there a way to verify the drive that an FE is opening from and then close if it is not where is should be?
I have a frontend that gets copied to each users C: drive by a .bat file. However, some just don't care about rules and proceedures and continue to open the frontend on the network drive. Since they map their drive to a specific letter drive for the BE that is where they are opening the FE from.
Can I keep my queries in the C drive and execute it against tables that are in the LAN network drive ? Right now the queries are also in the netowrk drive. So each time when I refresh the data into C drive, I have to import the queries too.
Is it possible to keep the queries in the C drive and execute against data in the netowrk ? Please let me know.
Hi. I have been searching previous threads and the help file and got half way, but have got stuck.
I want to copy all files from a floppy disk to a drive on a directory on a server. I can check to make sure the directory exists and if not, can make it. All I want to do is copy all the files from the floppy disk drive (A drive) to the direcory I have just created.
I have my database connected to a network of ten computers. I recently switched my linked tables from a Mapped Network Drive to using the actual UNC path \computerfolderdatabase.mdb
My users have started to notice it takes longer for the database to connect in order to log in. Once they have established the connection, the data transfer speed seems to be normal.
Is this to be expected? Any suggestions to speed things up for login? Or is this the downside to using UNC?