So i want to protect the back end of a database but im limited to what I can do....I am unable to restrict members from accessing the file by username...I am unable to place it in a local area which is pass protected...I am also unable to encrypt the back end as the front end needs to be able to access it (and I dont know how to allow it to do that...)
I plan on using Excel as the front-end and Access as the back-end only. (all queries and forms are in Excel). A single Access database will be queried from multiple Excel files that will be located on the share drive (Linux server). Access tables contain memo, text and number fields. Data will be sent to Access tables and records will be appended/deleted; all via Excel.
There will be multiple users interacting with a single Access database via multiple Excel files located on the shared drive. Users will be interacting from different workstations with Windows 7, all have Access 2010 and Excel 2010 installed.
This process works for me from my workstation but I am not sure what will happen when other 4 people will be sending/appending/deleting records to the same Database? How do I make this work? What settings do I need to check in Access to make this possible?
I have a database which is split so that several people can have a 'front end' to the database to access one common back end. This works fine on a network but I thought I could load the backend up to my webspace and then with the links manager point to it, but it doesn't work. I get an error report of 'not a valid file name.'
The website is [URL] .... and the backend database name is Probus_data_A.accdb and so I entered [URL] .... as the address in link manager.
I have created an access 07 database and split it to a back-end and a front-end with linked tables.
I wish to deploy it an a network of 4 computers, 3 of which are running on XP. The back-end will be on a computer running on XP. Now, from the instructions I have come across online, the Back-end has to be located on a folder where all users have Red and Write rights!!! And I am thinking, if the users on this network can actually see the back-end since it is on a shared folder where they have all the rights, then does that not compromise the security?
Is there a way of linking to the back-end on a network WITHOUT the users being able to access the back-end?
I am trying to use VBA to backup the BACK-END of a split database (so I can automatically archive selected data). If I use FileCopy I get a message that the BACK-END database has not been found.Obviously I could 'unlink' the BACK-END, copy it and 're-link' it..Is it possible to copy the BACK-END tables(not just the links) into the FRONT-END and get at them that way?
I am using access 2007 and my backend DB has a lock on it while every user has said they are not in the front and back end db's. Is there a way to remove the .laccdb lock? I need to modify my backend and this is holding me up from making any design changes.
I have a split database. I have secured the mde sufficiently but I need to secure the back end so that no one could link to tables in it. If I introduce a password to the back end is this going to require those using front end to supply the password? If not then this could be good solution.
As the database is on the network drive, is there any other way to prevent people to link to the db? Can I hide the db in the network drive? Or should I hide tables in the BE. Should these still be available to be linked?
Using Dropbox to host a split database. Ulimately I would like to create a run version for users with the back end held in a drop box directory.
As an unsplit database everything is working fine on dropbox records are saved in a timely manner and great.
Once I split to FE /BE only some records are saved on the BE and some are dropped. Was getting conflicted copies of Back end but manged to stop this happening but the records were noit on either copy.
Gave each user their own FE (on a drop box directory) linking to a BE in a sub directory on the same dropbox.
The key issue is that not all users have access and I don't want them to get into code so want to aim towards a run version.
The front end has been saved in a accde format and distributed to 20+ users. They have all saved this onto there computers and this is used as an application.The users complete a form on a weekly basis on the application and then save. This then saves into the back end.For some reason I have noticed that a few users submission randomly do not save. For the life of me I cannot understand why.All users have saved them into the back end in the past but every now and then submission for users do not save.
I have a Access data base (2007) which i splitted and store the back end database in a file server where all users have full control and the individual copies of front end put in the users computers. Unfortunately when one user is using the programme, others can not use. Following error msg appears. Both back end and front end are running under shared mode ( not exclusive ).
"Could not use xxxxxx_Be.accdb; file already in use."
I have designed a split database( with back end and front end), I am just wondering what would be the best way to put a password for both of the back and front end.
I have split my database in Front End och Back End, and both are password protected. The Front End has been converted to ACCDE.
When I try to import to Excel from Front End and/or Back End using database connections I receive a message telling me that I am using an invalid password (even though I use the same password when I encrypt/decrypt FE and BE). I've tried using Access import, ODBC and Microsoft Query. (In some cases I 'm also prompted to set a username, which I do not know which it should be since I haven't set one in my database (except the automatic "admin"))
I have a database that has been created for a company - all of the queries they need to run and changes they need to make to DB data is done through a series of Forms. Is there a way I can make it so all they can do is access the Forms (so they can't right-click and edit the form or edit any code etc.)
I have built a Access solution for a music school, It was installed on 3 machines.
I'd like to protect my database from installing onto another machine without my permission.
I did install database as a mde file so they cannot see my codes. However, if they copy the database to another machine (esp. another machine in different school) they can use my software without my permission. How can I prevent this? If they copy the mde file into unauthorized machine, database should work as a demo version (such as limiting the number of records in tables to 10). How can I do this? What should I check, hd id, mainboard serial or what? Is there any ready solution (at least modifiable) for that kind of problem?
I designed and distributed a database client to a bunch of users. They have asked me to password-protect it so that anyone can open the database and view the forms, but a password is needed to actually make any updates. I am trying to do this, but everything in Tools--Security is making my head spin. I have actually already managed to somehow lock myself out of my own database, although I have another copy.
How do I set the Workgroup Administrator Files so that they apply to anyone? It wants to put a separate file on my C: drive, but I don't use this database, I distribute it to people who do. (The server is on a share drive, can I put the Workgroup file(s) there?)
What settings do I modify to require *anyone* to need a password to update? Or is that even possible? I don't really want to break up the users into different categories.
If anyone could walk me through this process I would really, really appreciate it.
Cannot open back end database. There are no other users logged on Tried opening it in open exclusive mode but still error message. Front end on number of desktop PC's. Back End on server. I need to get in design mode on back end but won't let me. I get logon screen but when try to log on get message below I can log onto front end ok.
Error message something like.
* You do not have perimission to open or enable database * You must have open/run open/exclussive administer permissions. * Request other users to log off e.t.c.
I need to take my database 50 miles to a factory site so that an engineer and I can review/modify all the records, ~450 so far.
Can I copy the front end and back end files to my laptop, review edit the data offsite, and then overwrite the back end file on my server when I get back? Are there any issues with doing that?
Does anyone know of a way to make a database back up by a click of a button in a main form in the database? (so a customer does not have to go tools/database utilities/back up database)
We are currently running a FE / BE splitted database abd would like to back the back end up (to a sepearate location) every 15 minuutes by using the On Timer event.
Troiuble is, I believe I cant use the CopyDataBaseFile method whilst other users are in it and it would be too much hassle kicking everyone off!
Manually copying and pasting is good, but would really like to crack this one
I have done the mistake of not keeping a backup, what I did is split my database file access and then created my mde file, I need to change some data on my tables, but I get the msg that I cant edit a linked table, is there a way that I could put things back the way it was, also this path that was created is it possible to change for future purposes (I might have to move the dir into a different path)
I have been asked to take a database created last year and re-design it to make it more user-friendly. Not a problem, I thought when asked but I am running into a little problem...(the database designer) In my opinion, to make a system more user-friendly there is a necessity to access the code and tables in order to gain a reasonable knowledge of the way in which it has been constructed. Unfortunately, although I am allowed to LOOK at the front end, I am not allowed any further access to coding or back end information. At present middle management are siding with the database designer as they feel that from a security standpoint, access needs controlling (I can agree with this to an extent) Does anyone have any ideas of how I can talk the management round or any suggestions for a way through this issue? (Oh, and I'm not allowed to build them a new database and substitute it...I already asked)