Access Front End/Sql Backend - Access ramdomly needs to shut down | Member | | Join Date: Aug 2009
Posts: 46
| |
I have about 20 users in a database that has an Access frontend and a SQL backend. All of the users are in the database at the same time entering data. There are about a handful or so of the users that will get the Quote:
Microsoft Office Access has encountered a problem and needs to close. We are sorry for the inconvenience.
error when they are typing a large comment in the comment field. It doesn't happen consistently and it's only when they're entereing a comment in the memo field that's very large. We tried updating the database to 2007 but that didn't work. We did a repair and compact and that didn't do it either. Any other suggestions?
|  | Moderator | | Join Date: Nov 2006 Location: Richmond, Virginia USA
Posts: 2,992
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
Quote:
Originally Posted by stateemk  I have about 20 users in a database that has an Access frontend and a SQL backend. There are about a handful or so of the users that will get the error Is this a single front end, shared by the users, or does each user have their own copy of the front end on their hard drive?
Is it the same handful of users each time?
Linq ;0)> | | Member | | Join Date: Aug 2009
Posts: 46
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
They all use the same single front end. They just have a shortcut on their desktop.
Yes it is the same handful of users.
| | Moderator | | Join Date: Nov 2006 Location: Richmond, Virginia USA
Posts: 2,992
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
First thing to do is to correct this! Each user needs their own copy of the front end on their respective hard drives. Multiple users on a single front end can run into all kinds of problems, including what you're reporting as well as timing problems and outright corruption.
This particular problem may be caused by something else, but separate front ends is a must, regardless. After doing this, see if the problem resolves and report back.
| | Member | | Join Date: Aug 2009
Posts: 46
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
I'll give that a try and let you know. Thank you for your suggestion.
| | Moderator | | Join Date: Nov 2006 Location: Richmond, Virginia USA
Posts: 2,992
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
Like I said, it really needs to be done, whether or not it's causing this problem, because sooner or later it will cause you problems.
Good luck!
Linq ;0)> | | Member | | Join Date: Aug 2009
Posts: 46
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
I tried splitting the database. I followed the instructions that Microsoft gave. It created the backend table, however, when I finished with the wizard, it said the database would be empty as there are no tables in the database. There are six linked SQL tables in the database before it's split. Why is it not picking those up?
| | Expert | | Join Date: Jul 2009 Location: KY
Posts: 245
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
Your DB is basically acting as a front-end now, since all the tables you are connected to are on a server, so there is no need to split this DB. The definition of a front end is a DB with linked tables, which is what you have. When you split a DB it takes all of your local tables and places them on a back-end DB and then links your front-end to them. In this case you have no local tables so the back-end would be empty.
What linq was suggesting was giving each user a copy of that front-end you were attempting to split.
Hope this makes sense,
-AJ
| | Member | | Join Date: Aug 2009
Posts: 46
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
Does anyone have any other suggestions with this matter. I have tried updating the database to 2007. I also updated the user's computer. She still periodically gets the error when entering a comment in a memo field.
| | Expert | | Join Date: Jul 2008 Location: Maryland
Posts: 1,160
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
When you say the error occurs when entering a very large comment, how many characters are you talking about?
|  | Administrator | | Join Date: Oct 2006 Location: London - UK
Posts: 15,696
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
Quote:
Originally Posted by stateemk Does anyone have any other suggestions with this matter. I have tried updating the database to 2007. I also updated the user's computer. She still periodically gets the error when entering a comment in a memo field. Have you done what Linq & AJ took their time to explain to you? You don't say.
| | Member | | Join Date: Aug 2009
Posts: 46
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
Yes, I have done with Linq & AJ suggested and the user is still getting the error.
ChipR, I'm not sure exactly how many characters. The user doesn't keep track. I'll have her start counting the characters and see if there is a trend there. Thank you.
| | Expert | | Join Date: Jul 2008 Location: Maryland
Posts: 1,160
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
If it's less than 64k characters, then the problem shouldn't be related to the length. You never know what people will paste into fields, though.
| | Member | | Join Date: Aug 2009
Posts: 46
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
I don't think the user pastes anything. I'm pretty sure she has to type it all in and that's why it's so frustrating for her since she'll be in the middle of a long comment and it will just shut down on her.
| | Expert | | Join Date: Jul 2008 Location: Maryland
Posts: 1,160
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
Is there anything listed in the Event Viewer in Administrative Tools after the error occurs?
|  | Expert | | Join Date: Sep 2007
Posts: 271
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
If the form isnt too complex, I would try recreating a new copy of it from scratch. Any vba behind it can simply be copied over from the existing form.
With all those concurrent users operating out of the same front end, you've probably gotten a bit of corruption in there that the compact/repair didnt catch.
If that doesnt work, then you need to narrow down what exactly triggers this, if it's character length, if it happens every single time, etc. Make it reproduceable.
| | Administrator | | Join Date: Oct 2006 Location: London - UK
Posts: 15,696
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
Quote:
Originally Posted by stateemk Yes, I have done with Linq & AJ suggested and the user is still getting the error. For clarification MegaLog, Linq's suggestion (referred to in quoted post) was to ensure all users were using a different copy of the FE database so that should no longer be causing any issues.
| | Member | | Join Date: Aug 2009
Posts: 46
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
The user is going to try to keep track of how many characters she's entering when the error occurs. She said she does paste comments into the memo field from time to time, but that she has never gotten the error when pasting, it's always been when she's actually typing. The following message comes up in the log when she gets the error, but I can't find anything specific on it. Quote:
Faulting application msaccess.exe, version 12.0.6423.1000, stamp 49b08a47, faulting module mso.dll, version 12.0.6425.1000, stamp 49d65443, debug? 0, fault address 0x00005154.
Quote:
Bucket 1257631902, bucket table 1, faulting application msaccess.exe, version 12.0.6423.1000, stamp 49b08a47, faulting module mso.dll, version 12.0.6425.1000, stamp 49d65443, debug? 0, fault address 0x00005154.
If I were to recreate the database, would that help since not all the users are getting the error?
| | Administrator | | Join Date: Oct 2006 Location: London - UK
Posts: 15,696
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
That sounds to me like it may even be a HDD issue. Maybe a faulty sector.
Buckets are a unit of data storage in a database that the system manages for you. If it only happens on the lady's PC then it's probably hers that has the problem. Does she ever get the problem if working elsewhere?
| | Expert | | Join Date: Jul 2008 Location: Maryland
Posts: 1,160
| | | re: Access Front End/Sql Backend - Access ramdomly needs to shut down
If the memo field is indexed, be sure to delete the index.
|  |
Similar Microsoft Access / VBA bytes | | |  /bytes/about
We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights.
Get the best answers to your questions from over 226,295 network members.
|
