I've created a database on put it on a shared network drive. I have several people who will need to use this database but I dont want some of them to be able to edit the database in anyway.
Ive tried creating individual user accounts for the database but I don't think I'm grasping how the security works.
When on my machine I'm promted for a username and password but when on someone elses machine they can open up the database with full access.
How do i create individual user security accounts on a database I want to share on a network drive?
I need securing an Access database. I am about to put the database on a shared drive. I want myself to be able to do anything (of course), my co-worker Paul to be able to ONLY enter information (along with being able to view everything like forms and reports), and my boss to ONLY be able to view everything (form/report wise).
I found this post [URL] .... about how to secure a database. I spent all day doing it, but it didn't work at all! I just got a bunch of errors whenever I tried to do anything, so I deleted the database and re-used an earlier version.
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.
I have a order database and i receive invoices from suppliers and there are different users updating the records. I want to save the invoices in shared folder so all of the users can view/access the invoices.
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 have a form displaying records. I would like the user to be able to select a button, browse for a file on a shared drive and link it to that record.
I have been exploring hyperlinking, which works for the most part, although I need it to display the share name rather than the drive assignment for that user. Such as drive1folder rather than C:folder.
Hyperlinking also unfortunatly requires the user to right click on a field select edit hyperlink then browse.
I am going to put my access database on a network drive so that four different computers can have access it. However will user-level security work if I implement it? For example, from one of the computers I implement 2 different usernames and passwords. If one of the other computers tries to access the database will they also be presented with the logon screen?
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 been having issues dealing with "moving servers" addresses, file relocations, and folder name changes.
this makes 'linking' quite difficult.
I came up with this option, and am wondering if this would work.
'Delete old table connection DoCmd.DeleteObject acTable, "ExampleTableLink"
'remake them based on current location. DoCmd.TransferDatabase acLink, "Microsoft Access", Application.CurrentProject.Path & "DatabaseName.mdb", acTable, "ExampleTable", "ExampleTable"
Basically, this code deletes your current link, then recreates it based upon the path of the current database location. As long as the two databases are relativily equal in there locations, one could move the databases / be in completely different locations, and the links would always work fine.
IE:
One computer has the location as w:database folder
Another has q:somewheresomehowIdon'tgetitdatabase folder
3rd example \serverWierdsomeplacehotcoolcheese.blue.orgda tabase folder
and the links would still be established correctly.
In fact, old broken links would be erased and re-established correctly.
I KNOW there are limitations to this.
For example... If this is run from A FRONT END, then the front end's current location is give as the current location.
Can anyone think of a way around this? Without user interaction?
The only option I can think of for this example would be to allow a user to manually run this "relinking" process by re-copying out a new user interface from the backend setup.
IE: If the current front end fails, tell user to go to backend location, open the "backup" user interface, on doing so, the links are re-established and a copy of the front end is put on user Computer with desktop link.
Don't really like that option though... too.. clumsy and dependent on user knowledge / skill.
I have a single database that I would like many people to use concurrently. The db will be stored on a security clamped network with my users logging on with there own individually user accounts.
Does anybody know the simplest way of creating a distributable user front end that would allow simultaneous use by many people?
I’ve read most of the posts on splitting and deploying Access applications but most of them appear to concentrate on networked backend databases. However, my case is slightly different and I would like somebody to confirm that I’m taking the best course of action to achieve my goals.
I’m currently developing a non-networked accommodation booking system which has some basic functionality that my end user is testing on their standalone PC. I am currently adding historic data to the data tables to allow the end users to make full use of their existing data when testing the new system. The application development is ongoing and I will be releasing updated versions of the system over the coming months and want to be able to release the new features without having to reload the most up-to-date data from my user each time.
Therefore, is the best approach to:
Add the historic data to my development. Split the Database giving front and backend databases. Initially deploy both front and backend databases to the end user. Continue with the development on the split system and when new features are added just deploy the front-end database to my users leaving their data tables in tact on their machine.
hi.. i have a database stored on my main computer. all pcs on the network have windows xp.the database is stored in a shared folder.. and at the moment.. everyone on the network can open the database.. but not at the same time..basically if i have the database open.. my colleague on the pc next to me has to wait till i close it.so what i am asking is can someone direct me to a simple tutorial or some reading material..that introduces the methods needed to allow multiple pcs to access a single database with or without a login system.i imagine there will be certain read/write and locking issues.. but i really need it.thanks.
I have just been told that we shouldn't be using Access to build databases for sharing information. Instead it should only be used to build single user databases. Please, give me some ammunition to show what a stupid statement this is!! :eek:
I've read and gone though quite a few of the scrips and examples for creating logins and security and i'm getting to the stage when i need to have good understanding of the different methods.
Some of the examples whilst create a user login do not really allow for security within the database whilst the build in security wizard would appear to offer that functionality.
I am thinking that I will use the Workgroup file and that method. My question is am i able to utilise the fact that if a person 'AdamA' logs onto the database which is built into the workgroup security file. am I then able to take 'AdamA' to populate a table which records actions by a user? (I can't seem to find any thread or book reference to doing this)
can anybody tell me why my colleague cannot add records to a DB I set up on my pc.
i have a DB with 3 tables linked (all one-to-one).
i can add records into it fine on my pc but when my colleague tries on her pc it allows her to enter data but when it comes to moving onto the next record it wont allow her to save the record.
To explain further. there are 3 tables as mentioned before. lets call them Table 1, Table 2 and Table 3. When my colleague uses the form to add a record it wont let her save it as it says a related record is needed in table 2.
any ideas why it works perfectly on mine but not on hers?
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.
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?
there's a database in a shared folder (two pc connected NOT in a LAN). the database is on the pc called "A", i'm in the other (called "B") ; i open the db and i've a message "read only". so i cannot enter, modify, ... how can i give to the pc "B" the possibilty to modifiy the db??
Im having some problems sharing a database. I need multiple users to be able to open the database at the same time. I have check TOOLS - OPTIONS - ADVANCED and my option is set to shared, but for some reason it will still only allow 1 user to open it at a time. Does anyone know why this could be?
I have a big problem and it's stopping us from rolling out the db to our call-center... cliff-notes at the end...
I have a database that tracks customer calls. The db files are located on the network in a folder that everybody has access to.
The db is arranged as such: A backend that holds all the tables. A front-end for Customer Service Reps with tables that are linked from the backend A front end for Managers linked in the same way. And a front end for our corporate folks which is also linked in the same way.
I've tried replicating, making mde's and creating a shortcut on each CSR's desktop. I've also made sure that I use the UNC to link the tables. I've also made sure the db's are shared (I think)
Cliff-notes: when I have the front-end open on my desktop, and somebody else tries to open it, they get an error. "The file is already in use"
Am I doing something wrong Or am I missing some type of setting??
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.
