Hi
can i put a password for a backend database without affecting the front end?
i have in the past put the backend database on some secured drives and i had problem with the front end. My main concern is to protect the backend which sits on a drive that has no security with it at all.
Any help or suggestion will be highly appreciated
Thanks
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 ;)
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)
Is it possible to do this through vba. If security is setup for all the tables and a user goes in and creates a new table, can that table have security applied to it using code?
So maybe the creator of the table has read/write privileges but everyone else only has read only.
Hi all. I know Access security has been discussed ad nauseum in these forums and that there is a wealth of information in the archives, nearly all of which I have read often.
And I have a small question.
For years I produced applications which didn't need tight security. However, I tried to stay well informed on the matter.
Security is important in this project. I secured a database properly, as well as I can determine. I then made a copy and deleted all the tables in the one which will be the frontend and linked to the tables in the copy which will be the backend. Only Groups had permissions, individual Users, none. Life was good.
Then I did something, not sure exactly what. The end result is that the frontend seems fine; I cannot open it unless attached via the .mdw I created specifically for this project.
The backend, however, I can open even when attached to the system default .mdw.
Can anyone tell me what I've likely done, and how I might nail down the backend once again?
I have been given the responsibility for a database that resides on a company network. The Database has been created by using Access 2000 in Windows XP. There are windows folders fro each team that needs use of the database and within these folders is a macro that loads the form for each team. There is a shortcut folder to the Admin Entrance point wher the actual database and tables_be are located. I have looked at both the properties of both these files and both are Access 2000 databases?
The Database called Database( not my choice of name ) contains all the forms, queries, reports,modules etc and the tables are linked to what seems to be the Admin Entrance point. Unfortunately I am unable to see the full link when using linked table manager. This I presume is the tables located in tables_be. The database table_be contains all the tables.
When trying to store the Autonumbering to the database after corruption using a solution kindly supplied by Pat Hartmann by taking a copy of both the database and table_be and working on these I successfully got the autonumbering working.
What do I need to do to successfully implemting these on the network. I have tried to copy the new files back to the network with the same names and in the same location but am getting error messages when I try access some of the forms.
Unfortuately there is no documentation as to how this database has been constructed hence the long winded post.
I have a database with backend tables. I came back to work today and somehow the main table in the backend has been corrupted. I tried to repair the table in the Backend and I get the following error Could not find field 'Description'..
Now when I try and open the Backend I get this error. The database 's:SOE_CONTROLSoeControlDatabaseBackendew_1-8T_SOE_DATABASE_be.mdb' needs to be repaired or isn't a database file.
You or another user may have unexpectedly quit Microsoft Access while a Microsoft Access database was open. Do you want Microsfot Access to attempt to repair the database?
When I click yes I also get [B]Could not find field 'Description'.[/]
Each time I have done this another DB1 or DB2 or DB3 or DB4 table has been created. When I look in the tables I can see that somehow there is a deleted record and it will not let me delete that record. I delete it and then open the table again and the same deleted record is still there.
I hope this is making sense because I sure need help!!
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 an Access 2000 split into FE and BE and the client has requested the BE be password protected. I attempt set database password on BE but then when I open FE I get error msg " not a valid password". I get the same error message if FE has same password or if FE has no password. Any ideas?
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?
I have split db with the backend residing on a computer in my workgroup in the shared files folder. I have access to the folder and can view the file perfectly fine on the other computers in the workgroup (a wireless 54Mbps network). The problem I am having is that almost every time i access the backend tables from another computer in the workgroup, access freezes up and has to be shut down. Sometimes, after restarting access it works fine, others not at all.
Any suggestions or help would be greatly appreciated.
I managed to password protect my backend (as the backend is on a server and anybody could access it) so i have it password protected so only i can gain access to the data. Now, when i try and access the backend from the front end, the frontend prompts me that the password is invalid (indicating its trying to enter the backend using no password, thus an invalid password warning appears. And this means nobody can access the data from the frontend)
Is there a way to get round this password issue from the frontend? I.e. have the password for the backend, but when you access the frontend, it doesnt need the password for the backend (i have my own username/password system to log on to my database)
I know there are different user level securities you can use, but im not familiar with this. So if you have an idea about this, then im all ears but keep in mind I don’t really know how the security levels work in Access (nor do i have the time to learn it in depth or even find help other than here)
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.
This is a bit of a weird one I hope someone can help with. I have a fairly small db that needs 3 con-current users. It is split and until recently, the backend resided on one of the computers in the shared folders directory. In this configuration it worked fine, but just recently I have set up a network using a Mac OSX server (xserve) and it is causing a bit of grief. It seems that only one user can access the backend at a time and I have tried just about everything listed in these forums with regards to permissions etc. One bizarre thing is a post here suggested I join/create a new workgroup, did that, stored on the same shared directory on the server. Every time one of the other users on the network joins the workgroup, then re-opens the frontend, they are still logged in as Admin, not the new user recently created. The folder where the workgroup file and backend reside definitely has no access restrictions. Is it something to do with the Mac environment or something else. The only way around it so far is to log 2 of the computers to the server as the same user, this sort of works. Another weird thing is every time one of our users opens the frontend, a new workgroup file is created, system1, system2 etc. Is this normal?
Any suggestions you might have would be greatly appreciated.!!
I have an MS-SQL backend which i use for my data source. I then use Access for reporting services. (It works so much better than SQL Reporting Services 2005).
this seems simple, but i can't get it to work. Everytime the users start up access, It pops up a login and password for the ODBC link. Even when i have the password and login setup in the ODBC DSN, it still requests it everytime you start connecting to the datasource.
Is there anyway to somehow hard code this into the Access front end somehow so i don't have to give the password to the users?
How do I link the backend tables to the front end so it works everywhere? I mean right know it says C:ewprojectackend.mdb how do i change that to newprojectackend.mdb ?
I'm currently researching on how to best migrate from Access back-end to a SQL backend, and was able to find wealth of information on how well Access can play with various SQL servers, how ODBC drivers are implemented, and how JET handles queries to backend. If this helps matter, I'm considering using MySQL as a backend.
That said, there are some gaps in my research that I'm hope someone will be able to fill in for me.
1) I have couple of queries that may use Access's custom function not otherwise supported in SQL servers. If I based the query on otherwise executable query, would JET be able to pass the sub query to SQL, and get the recordset and apply the next query using custom functions without any problems?
2) In general, DAO is best when you're using JET, but ADO is best for ODBC. I'm not clear whether it's possible to use a mixture of ADO and DAO, provided I've disambiguated the library (which I already did anyway) to make even efficient use of recordset. For example, I'd use ADO to work with data from backend and once it's bought over here, switch to DAO for faster handling by JET. Is that possible *and* advisable?
3) I found lists about limitations or problems that may arise due to differences between Access and SQL, which is good to know. However, I never found any answer as whether VBA may cause problems with using SQL data. Let's say I have a form that has lot of VBA coding to handle calculations, multiple selection in listbox to be added to a junction table, dynamically changing rowsource for a combobox, whatever that is based on a query that otherwise runs fine with SQL server- will the form still work just as fine or are there going to be any surprises after migrations?
4) Somehow related, if this is supported by whatever SQL server I may use, would I be better advised to use stored procedures in place of VBA for Access forms?
I have a VBA script that opens a intra net web page and downloads data from it. The data is stored locally in Access tables. After the tables are filled, the script ftp's the database to the web. This script is set to run every night at midnight and has worked well for months now.
I had to upgrade my website's database to MSSQL server from MS Access. So now my script needs to be modified. I need to take these access tables and upload them to SQL Server instead of a simple ftp upload.
In SQL management studio I can import an access database easily. It transfers all of the data in 5 minutes or so. But I have to do this manually and click through a wizard.
I have tried setting up linked SQL tables and running append queries with VBA using DoCmd.RunSQL This method is way too slow. I tried saved append queries using query design grid and it is only a little faster.
I am transferring 10 tables or so, with anywhere from 1000-100,000 records. I've read through 3 pages of SQL Server searches and I am still at a loss. I really need to automate this process.
Hi - I have a front end database that is linked to 2 backend databases. I'd like to add code so that after the splashscreen pops up it checks to see if the front end is linked. If not then asks the user to enter the path for the two backend databases. I need your HELP!!1
Quite often I'll make a "training" version of the backend database so that people can "play" (or should I say get training) on dummy data without them having to worry about ruining the live data.
If my real data is in a file called RealData.mdb and my dummy data is in a file called TrainingData.mdb, I want to display this name prominently on my menu form. Thus they can then change the link on the front end to the real or dummy data as required BUT have a reminder as to which they're on.
How can I do this? Further rather than using the file name, could I use one of the database properties (say Title) to display a more friendly text name?
A client has had a database in operation for about a year. They requested some updates. I have been trying to figure out an easy way to update table structer with out having the client go into the backend and add a field or two.
I wrote an update program, that copies the table from their backend, and copied it to the updated table and tried to copy it back to thier backend, but since it is in a relationship, it won't let me.