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 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?
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?
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
I know there are posts on forums all over the internet on this topic, but it is just one aspect in particular that I would like some simple advice on. I have worked through user-level security suggestions online and made a test back-end database that has a user and a group, named "Developer." All of the privelleges are activated for Developer. Developer is the only user who can access the data of "Table1." I've created an RWOP query that retrieves the data from Table1, Developer is the owner of this query. I've also created a front end and tried to create a link to Table1; which is denied, as I had hoped it would be. My question is this: How should I structure my front-end so that users can retrieve data from this query, but cannot obtain the data using a different front-end?
I am developing a 2010 database which is split. In the back end I am linking to csv files - with a new file every month to link to.
What I would like to do (and have not been able to find a way to do at all so far! ) is each month to add the new table link in the _be and to be able to choose it in the front end user interface to view reports on, without having to "re-programme" the underlying queries to use the new linked table.
I have a Back end (with password) which resides in a netdrive while the front end is installed in each individual users desktop, the problem is, some of the users netdrive was mapped in a different way (different letters..some are J others are G). I'm looking for code that I can relink the database to the front end in runtime, I did try to look in the net but I can't find anything that I can put the password as parameter.
this sample code from Dev is good, but i got an error because the database requires a password.where i can put the password?
Code:
Function fRefreshLinks(NewDbName As String) As Boolean Dim strMsg As String, collTbls As Collection Dim i As Integer, strDBPath As String, strTbl As String Dim dbCurr As Database, dbLink As Database Dim tdfLocal As TableDef
I have built a Database links to multiple back end databases. The whole database is completed, and I have to share it across the company, so I have placed the Database and all of the Back End databases on a "public" shared drive. I have the "public" drive stored as my Q drive. So when I link to the back end databases, the path it stores is Q:DatabasesDatabase.accdb
However, the problem is that not everyone will have the "public" drive mapped to Q. It's possible they could have it mapped to P or A or whatever. So if someone has their "public" drive mapped to P, this database will not work (since Q:DatabasesDatabase.accdb would not exist for them - it's really P:DatabasesDatabase.accdb).
Is there a way around this? So that instead of it mapping to the relative letter (Q or P), can it just refer to "public"?
I have recently created a db for a large Printing operation in our company. Previously, the process was all paper-based and extremely inefficient, so obviously this is a huge step in the right direction.
Upon completing the db and providing a demo to the staff, I saved a copy to a shared folder on the network for them to access (.accdb file). We've done this with other dbs before, but with smaller groups (3-4 people). With this db, since there will be anywhere up to 15 people that may want to access it at the same time, the db started crashing during the first phase of pilot testing this week.
I did some more research and found that the db should be split.the users can't open the db anymore.I have a Printing Services shared drive in which created an "Administrator" folder for the back-end (the front-end is in the same location as that folder). When I split the db, I select the back-end location to be within the Administrator folder.
TrackerAdministrator OnlyOS Tracker_be.accdb" is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.I know that the file path is valid, b/c I selected it specifically when using the wizard to create it, and I know that the staff have access to the shared drive as they had to open it in order to gain access to the front-end. Plus, it's working for me when I try to open it, just not the others.
I'm sick of the lame excuse for error messages that Access gives out.. I'm talking about 'Overflow', 'invalid use of Null' and such like.
What about telling you what field/expression caused the error and on what record if applicable.
It's so frustrating - Access obviously knows what caused the error but refuses to tell you so you have to go through the annoying process of taking out fields one by one (when in query view).
Does anyone agree that they need to make the error handling in Access much better?
Could someone please help me trouble shoot this error:
"The Link MasterFields property setting has produced this error:'A problem occurred while Microsoft Access was communicating with the OLE Server or Active X Control'
I get the error when I try and select an item from a drop down list in a combo box on a subform that is linked to another form. The list is coming from a separate table.
When running the subform without opening the parent form I can choose from the combo box and do not get the error.
We have offices in other states that need to be able to open our data base. Due to the line speed it is extremely slow linking to our backend. Is it possible to have duplicate backends that can be merged, lets say over night or at the push of a button.
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 currently manually run a compact and repair on the backend of a database at work, but was wondering if it might be sensible to set it to compact on close so that (in theory) it is done at least daily and therefore shouldn't take much time?
The back end resides on a network server, which is backed up continuously, so in theory it should be easy enough to roll back to a backup copy should anything untoward happen.
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 have a form and subform linked by the ID field (AutoNumber) on the Form and Record ID field (Number) on the subform. I have the field size on the Record ID field set to Long Integer.
When the form is opened, a message pops up "The LinkMasterFields property setting has produced this error: 'Ambiguous name detected: Add_client_info_Click' There was a macro set up with the name Add client info. However, that macro is not being used on either of these forms. I don't understand why this message is popping up.
Any ideas? I have checked each form, each form section and each field to make sure that macro didn't somehow get assigned, and I can't find it anywhere in relation to these 2 forms.
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've created a custom ribbon for my end users (Access 2010) and everything looks and works great except for one issue that is becoming a deal breaker for me and my end users:
I've got a number of tabs on my custom ribbon and on each tab there are a number of buttons that open various forms and reports. Anytime one of those forms or reports is opened and then closed, the ribbon jumps back to the first tab in my custom ribbon. So if you were on tab 3, opened a form and then closed it, you would be jumped back to tab 1.
Any workaround for what seems to be "by design" behavior for custom ribbons? The built-in ribbon does not do this.....
