Access Front End/Sql Backend - Access ramdomly needs to shut down

[stateemk]

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

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?

[missinglinq]

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)>

[stateemk]

They all use the same single front end. They just have a shortcut on their desktop.

Yes it is the same handful of users.

[missinglinq]

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.

[stateemk]

I'll give that a try and let you know. Thank you for your suggestion.

[missinglinq]

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)>

[stateemk]

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?

[ajalwaysus]

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

[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.

[ChipR]

When you say the error occurs when entering a very large comment, how many characters are you talking about?

[NeoPa]

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.

[stateemk]

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.

[ChipR]

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.

[stateemk]

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.

[ChipR]

Is there anything listed in the Event Viewer in Administrative Tools after the error occurs?