General :: Added Table To Back End Not Linking Up To Front End
Jun 22, 2012
I did a search in here as well as Google to figure out why when I relinked the front end to the back end after adding 2 tables to the back end that the tables did NOT show up on the front end. Only the original tables that I began with.From what I have read there are different ways to do it. One suggestion on here was to create the table on the front end and export it to the back end. I guess I will have to do this going forward.
But my question is, after searching pages upon pages with no luck, since I already have the tables in the back end how do I tell the front end to find them and link them?
My question encompasses a front end connected to multiple back ends. It is probably a mundane point, but reading a few articles didn't seem to touch on it.
By this, let me toss out that I am thinking of the personnel where I work when I say 95% have a hard time using email and MS Word, let alone mundane functions like find a file, etc. As such, I have to make my front-ends extremely user friendly.
With that in mind, when developers have multiple back ends, what are thoughts about the best way to relink when required? Even when there are 'more sophisticated' users? Security not an issue or is an issue (inasmuch as can be handled in access)?
Ex: Large corporation with a multitude of user ability. Large database with say 3 different back ends.
I was thinking about keeping a front-end table with each table name and UNC path, hard coding paths to corresponding table names, etc.
Personally I don't have a need for multiple back-ends, but the question came up while reading.
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
Objective?: I'm attempting to change the file location of the back end portion of my split database.
What I've done so far: I've used the linked table manager to update the back end location of all tables in the front end portion of the database.
Symptoms: When making a change to the OLD back end: If I change the name or move the old back end and then try to re-open the front end, Access opens as if I'm opening the application itself without any database associated with it until I restore the OLD back end to its appropriate state.
When making a change to the NEW back end: If I change the name or move the new Back end and then try to re-open the front end, I get a: "Could not find file" error message until I restore the new back end to it's appropriate state.
I've just discovered a query that I think put me one step closer to resolving this issue. [URL] .....
When I run this query:
Code: SELECT MSysObjects.Database FROM MSysObjects GROUP BY MSysObjects.Database, MSysObjects.Type HAVING (((MSysObjects.Type) In (4,6)));
It returns 2 results: 1. The path of my old back end 2. The path of my new back end.
Unfortunately I'm not able to update the values from the Datasheet, but this does confirm to me that the old back end is still some how being used by the front end even after my tables have all been updated.
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 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"))
Have a database with a back end that I have been working on. The database resides on a USB at the moment. I was ready to deploy and now when I try to re-link the back end tables, I repeatedly have the following error: "Your network was interrupted. To continue, close the database, and then open it again."
At first I thought this was something to do with the network, as I was moving it to a shared network drive. However, I can recreate the same issue using someone else's computer and using my USB (although it's mapped to a different drive letter). I've tried a few things, including recreating the back end by importing only the table structure, but still no luck.
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?
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?
