I work for a real estate company that uses Access to keep up with showing requests. I designed the database and I'm an amature. The database is fully functional but I would like to create some sort of log-on screen switchboard to restrict access to tables and such to me alone. I've got the idea behind the switchboard wizard but I want 2 or 3 passwords depending on who is accessing the database.
Also, I was trying to split the database but when I try to copy the forms etc.. database to another computer I can't edit the tables. I had the tables in a shared folder and allowed editing of it, but it wouldn't edit. Does the form database have to be stored on the same computer as the table database?
I think I am having some problem with my back end and frond end files. I have a mde file that anytime I enter new data or change some things in the old clients file, it does not update on the mdb file. Anytime I need to change forms or report or any thing at all, I am suppose to copy the BE file and the MDB file to my workstatio, remove the table link, make the changes I want to make on the design mode and then import the files back to the live copy of the mdb file then make another mde file to work with. But When I copy the BE and the MDB files, I don't have the updated client list or new client just added. So as not to affect other users, I can not make changes in the MDE file and even the MDE file will not even let me make any changes in design mode. I don't know If I am making sense but any help will be appreciated
I am having a trouble with a multiuser DB. I have split it using the Splitter Wizard and have put a copy of my FE to a second computer and relinking its tables. When I opening the bound form in computer 1, computer 2 can not open that form and sometimes computers lock and had to restart the machines. But if I open that form in computer 2 first and then the same form in computer 1 , it works fine. I have set full sharing to computer 1. I am using Access 2007 and Windows VISTA.
Both have FE, the BE is located in a shared folder with full permissions in C: in computer 1, the FE of computer 1 is in that same folder. Both computers are connected via a Cat5e Cable.
FE in computer1 table links to c:databaseBE and computer 2 links to computer1_IP_Addressc:/databaseBE
I've one FE & BE related question here. Ok first of all I've BE in server and each user have copy of FE in local PC. But I've one problem with linked tables between FE & BE.
Is there a way that FE can programmatically create connection to BE linked tables or user is able to link those tables manually, if FE can't find/connect to linked tables in BE? Or do I just have to manually configure each users FE linked tables?
All replies are welcome and well approciated at all costs! :D
Hope this isn't too silly, but I've just discovered "decompile". Instructions don't mention back ends and front ends. Do you have to run decompile on the FE and again on the BE, or is it sufficient to do it only on the FE (which has links to tables in the BE).
I have a db that I have split out into a front end and a back end. The back end is on a network drive, and I have a copy of the front end on each user's computer.
The issue that I'm having is that 2 people can open the front end and 2 cannot.
When the database opens I have a form that loads on startup with a username/password combo.
On the 2 machines it works on, everything loads flawlessly, on the others they get an error message stating "\networkpathaccess.mdb" is in use
I am about to place my database on a network. I have two extra folders in the database. The first contains excel spreadsheets that are lined to a form. The second contains .pdfs that are linked to a second form.
Where is the best place to put the folders, front or back end.
access 2000 with 30 users. 10 of which enter info. rest just use for reference.
I have all tables on network server all users get a front end access version with all queries, forms, reps, ect. Now I think I need to enable record locking but do not know what to do.
Do I enable record level locking for just the back end or only the front end systems? what is the best way to set it up? thanks.
Hi All I've been going through lots of posts in this forums, but could not find the perfect solution for my problem. I've got a front end database with forms. And back end database with data tables. The FE database is stored in all the computers with the linked tables in BE database in shared drive. I now want to totally disable the BE database from even being opened. The Data has to be so secure that people should not be able to open it(when they find out where the files are stored in). But it should still retrieve results based on data in BE database. I tried applying password to the BE .mdb. But it did not help running the front end. Instead came up with an error. Is there a way to restrict access to BE .mdb totally (as it is only a copy of the database I have in my drive). Any help would be greatly regarded. Thanks
Hi guys, I need help with security settings and that. I have a database which i want available on a shared server. Basically i only want people to beable to see one form but not beable to see anything else or make any changes to this form.
Do i need to split and make a front and back end? I will want to make occasional changes to tables etc.. and so would want this to automatically update on the database seen by everyone else.
Sorry, not making much sense but am bit confused about it all!
I have a live split db running which has recently run into a problem. When one user1 has a report open, user2 cant enter data into the table that the report is using. User2 gets a blank grey data input screen , apart from the form header. Similarly if User1 is entering data , and User2 tries to pull a report using the same table the message reads , could not lock table , currently in use by User1. Both Fes are on separate local machines.
I've had a check through my settings. On the advanced tab of Tools , Options default open mode is set to shared and default record locking is set to no locks.Plus open databases using record level locking is not on., both on FE and BE..
But, users 1 and 2 can pull the same reports simultaneously or enter data into the same table simultaneously but not one a report and the other enter data.
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 had posted this in another area but didn't receive a response and my whole project has ground to a halt until I sort this out :(
I have made a database with front and back ends. Now I wish to be able to use the front end over the Internet but the IP address of the back end keeps changing weekly because of my ISP. Now I have made a splash screen at the start of the program which asks for the IP address and when this is entered the front end links to the back end - but I can't get the code right for this
The code I have at the moment is embarrasingly wrong so I'm not putting it up here
The code I have at the moment has a box that asks for user to enter the IP address - I need it to use the IP address to enter the database at ip//data.mdb
I need help making a front and back end to my database. How should I do it!?!? All I know is what I should put in the front end and what goes in the back end. The rest needs to be explained to me somehow...
I have a database that I built as one large database, then used a method I found on here to creat 2 brand new databases and copy the tables from the original to one and use it for a back end and then copy everything else to another file to use as the front end. I did this and it worked great, except that now the information being input into the forms on the front end is not being recorded into the back end. I tried relinking the tables and it still was not working. Is there a secret step I missed or something I need to fix in order to make this work properly? The way I made the front end dependent on the back end was by linking the table from the back end to the front end. I checked the object dependencies and it shows those as being correct. Any suggestions or comments would be greatly appreciated!!! I am truly only a novice when it comes to Access and just in the past 6 months or so have been using it regularly.
I have an MS Access front-end with a SQL back-end database. It works great, I connect the MS Access front-end to the SQL back-end using a File DSN.
I have a few users (who are in the database the most) who get ODBC disconnection errors time to time. The cause of the error is not consistent, they seem to just appear out of no where. The table that reports the disconnection is not consistent either.
The only way for the users to resolve the errors is to exit the MS Access database, and then re-enter it.
I have had the DBA team analyze the SQL server, and it does not appear to be having any difficulties. We moved the database to another server (so it would be on a server with less traffic) and I rebuilt the File DSN. But the errors continue.
I will have the network team look into any errors, but I am not certain if they will find anything or not.
Has anyone run into this, and what resolutions did you come up with/work arounds did you perform? I am starting to consider upgrading to a Visual Basic .Net front-end, but wanted to see what options were left.
I found this snippet in a thread on a forum I don't subscribe to. I think I understand what it's saying but can anyone expand on the how's and why's please?
'Your front end maintains any attachments to the backend (ie first form open opens a recordset on the backend to force the backend ldb file to remain for the session - a known trick to speed up FE-BE setups) '
I currently have a front-end/back-end database, but at some point in time one of the tables has been modified and whenever the front end connects it comes up with a parameter request for a field that no longer exists. I have narrowed it down to MSysQueries, where there is a reference to this field. Is there anyway I can avoid this or change/repair the system table?
Thanks for all your help on my last post, again have a problem to update the application, Everything works well but then I need toadd an extra table on my app. At first I thought I can add a table on my Back-End but when I open the Front-End it wont update.
Can someone out there help me how to add a table on apps. from the ground up?
I have seen it done in the past but at the time my limited knowledge did not retain how to do it, it is connected through the odbc, im am running server 2000
what code do i use to connect and how do i set up the odbc
How to secure SQL data when my MS Access database must access it using linked tables. Generally speaking on the Internet, assertions that migrating to SQL is more "secure" are rampant; explanations of just how that is are scarce.
Sure I can restrict access and put different roles on different tables, then put different people in those roles, but that doesn't really do me any good. Ultimately I want to achieve the following: Allow them to do all kinds of stuff (including Update, Delete, Insert) using my access application, but I would NOT want them to have those same rights if they installed SQL Server Management Studio, or for that matter, simply created an ODBC connection using another access or excel application.
In other words, ideally, I'd like to have SQL server view my Access application as a user in its own right. Not sure if that type of impersonation or identity is possible to achieve.
I am new to using access and have customized a project management database for a friend's company. I need a way to auto relink the front end and back end databases when moved in the same folder. I am currently using Access 2013 and have already tried using the code on this site: [URL]...... Does this code not work for Access 2013 or am I adding it incorrectly.
