General :: Detect Broken Backend Connection At Startup
Feb 17, 2015
I have a split Access 2010 database. If the backend file is not accessible (for instance, if our shared folder connection is broken), I get no warning message at all when opening the front end. Just the home screen you would get when launching access from the Start menu. I was thinking of adding some VBA code to my startup form to give users a warning that there is a connection problem, but Access won't even load the startup form.
I have a Access FE linked to a Access BE on a computer. Whenever the user of that computer shuts off, the Access FE handles this in worst way possible: It spews a zillion dialog warning of 'disk or network not found' before my error handler even takes over.
Has anybody come up with a way to catch such situation?
Without putting a /CMD parameter value in the command line, is there any way to detect in VBA that the current state of the application is that it is executing from a scheduled task ?
What's happening is that my Outlook email is failing because a Namespace Logon method cannot be invoked when there is no user logged in. I must jump over that statement when running from a scheduler.
I have been asked to look into fixing a permissions problem with a database. The company has been in the process of updating the OS on our computers.
The database in question is stored on a shared network drive. It opens fine on a windows XP machine running Access 2003 but when the same user tries to open the database from windows 7 using access 2010, the message: "You do not have the necessary permissions to use the '<file path>' object. Have your system administrator or the person who created this object establish the appropriate permissions for you."
I have a string where alphabetical and numerical characters are mixed up. I need a string function where I can find the index of the first non-numerical character. I tried with the mid function but could not get it to work.
"The key or key combination ^{Break} in FunctionKey_SubForm has invalid syntax or is not allowed" - - The "FunctionKey_SubForm" is a macro in this database.
It only does it on my computer when I opens this specific database.
This database works fine (copied it elsewhere) on everyone elses computer and also when I use it one another computer, whether the database is on the server or on the C: drive.
Since it works fine on all other computers, it's a setting in Access which is throwing up the error (even if it is " invalid syntax or is not allowed"), not the database.
Database works fine after I click through it but it's irritating and I don't recall changing anything.
I have (on a company network) a FrontEnd .accde and a backend .accdb - currently ~ 10 users (some over wifi - slow!)The FrontEnd is becoming a rather large file ~ 10 MB and is also becoming slower.I am looking to separate this in to 3 FrontEnd files as to simplify and to lessen the file sizes etc.
My question is - are there any issues around a 3 x FrontEnd databases all connecting to 1 x backend database holding all the tables - over a network?
I have completed the split and have deployed the backend to SharePoint. The front end is sat on my (and others) machines with linked tables to the SharePoint lists. This is all fine and works well.
Although this database is deployed, I am constantly working on a local copy of the database in design I.e. Tables being updated with fields and relationships and new tables being added. The reason for this is that work wanted something workable putting out there now and that I just continue its development in the background.
What is the best way to update the tables on SharePoint bearing in mind that users are putting new data on there? I don't want to lose what they are updating and then I need to redploy the 'new' backend to SharePoint again (no doubt in the same location) as that's where the front end is looking for it.how I can manage this version control of the backend without losing data.
I am able to bypass the shift key so I can disable ribbon and all menus at startup.
But the issue I have is anytime someone makes a copy of the database or it is their first time opening it they get prompted with the security warning:
"Security Warning - some active content has been disabled, click here to enable"
and it gives them complete access to see the back end of the database because while that warning message is popped up ... before they click "enable" they can go do anything in the database including see tables, data, and vba.
Once they click "enable content" that first time the bypass takes effect and the ribbon and all menus disappear, but if they dont click it they can navigate all around the db
Code to automatically backup backend to any folder or media in Access 2010?I need codes to be backing up my Back-End automatically. I am using Access 2010 format.
I've always practiced to keep my backend table names to no more than 8 characters because of speed issues. Can this also goes for the server name? My current location looks like this now orld71-testing-aFinance..I am wondering if changing the server name with speed or is that only for folder names.
I'm making updates for the front end then i send it to 10 pc's in the office then i should change the backend location via linked table manager for every pc
So is there any way to let the user choose the backend location when he open the database nad then it will automatically update the tables link
I have to do this and I believe there is VBA code to re-link tables when needed that can be found on the web. My client needs access to everything because he will move on to another developer after this, so what I thought I would do is send him a private file that has the password for the backend and then just write the ADO code needed in the app's front end to connect with the password.
I have splited the system into foreend (FE) and backend (BE). FE and BE are located in different PC lying in company internat! However, I found there always give an error message 3219. And, nseems it is caused by not pointing correcly to the BE when I open tables, the syntax are as follows
Dim db As Database Dim rs As Recordset Set db = CurrentDb() Set rs = db.OpenRecordset("Invoiceyr", dbOpenTable) rs.MoveFirst rs.Edit Me.THISYR = rs!Invoiceyr
The 3219 error appeared at statement "Set rs = "what's the syntax of the path that I should include in the statement in order to point correctly the BE.
I have split a few different MS Access databases before with the BE on a shared drive and the FE installed on all users' local machine. In this instance, I have three ODBC connections bringing in data to my tool from an outside database once a day. Is it faster to store the odbc connections on the FE or BE when I split them?
I want to deploy an access database at a small office with 5 computers, small network. However I do not intend to create a server in order to have a domain etc. Operating system is win 8.1 pro. Should I use a homegroup or workgroup ? Would it require password in case of workgroup? Which is a recommended way to setup this and keep some security like a guest cant access these files?
I'd like to to import some large oracle tables from a remote server using "DoCmd.TransferDatabase..." on a daily basis. Currently, the system works, but my database is getting quite large (800 Mb) and I'd like to split off the tables to a back end database.
Is there a way to import directly to the back end database? The postings that I've seen seem to imply that one must first import the tables into my front end, then export them into the back end. Does that sound correct?
I'm at home right now, but will give it a try when I get to work. It just seems like there's got to be a more direct way!
Jon Mulder Department of Water Resources Red Bluff, CA
I have a Ms Access split database where in the backend database grows up very fast and needs to be compressed everyday. I have written a batch script to compact the same and have scheduled it to be run every night. But the script is unable to compress the backend every time since the users tend to leave the application open at the end of the day. Ideally i am looking for a command line script to forcefully close the back end database if open before attempting to compact it.
I searched on web but could not find a command line script for forcefully closing the back end database.
I have a question about connection strings. Basically I have an access front end and an access back end. It works fine for now, but when it gets rolled out, I don't want to have to manually relink the tables every time. Is it possible to hard-code the database connection strings for all the tables used in the solution as the paths won't change once deployed?
I have a back end 2002 DB. I would like to disallow access to this through odbc connection. Is there some way this can be achieved? Thie directory where it is located is unfortnately cannot be restricted as the front end mde also resides there.
I have access application which was running fine recently but for some reason everytime I run it now it gives an error on the adodb connection string saying compile error.
Its doing this on every adodb connection I have in my database.
I have tried registering the dao an ado dlls but still the problem persists.
I have a Access front end connected to a MS SQL database using a ODBC connection which is working fine of course.
When I compile it as a runtime version and install it on the business computer I get an error with the ODBC connection (I can't remember exactly what pops up). On the business computer I have installed SQL Native Client and in the ODBC added a System DSN (which works).
