Users getting kicked out of Access

[Newman]

It started a couple of weeks ago but it wasn't often. Now I get it maybe 4 or 5 times a week...

Some users get kicked out of Access with a popup saying that Access had an error and it has to close. There is a checkbox to repair the database, but it doesn't resolve my problem, with or without the checkbox checked. There is also a linked called "Click here!" in the bottom and when I do, another window opens with a very long text in hexadecimal (I think).

Once I had that problem and there was a message at the top, saying MSJET40.DLL. After installation of the last Jet patch, I never seen the message again. Now, the message says "Unknown".

What could it be?

I had a lot of trouble making the administrators to put the MSJET patch, and I don't think that they'll be happy if I asked them to look for all the possible patches. And I am not sure that this is the solution.

I've seen this on many computers, but not on all. A couple of them seems to get it more often than others. Some will even get it while Access is open but that they are not using it for hours. I retrieved all the timers just to be sure and it appeared again. Can't be the VBA then. Can it?

I just don't know where to look.

Thank you!

Note: Using Access2002, Windows2002, BE/FE, group/user security, 30MB(20MB-Data;10MB-Prgm) and 30 users but never more than 10 at the same time.

 

[Newman]

I had no answers and never found out what the problem is.
I run the thread again, just in case that someone knowing the answer might have not seen it the first time.
Thank you!

 

[Autoeng]

Have you tried the simpliest thing first? Create new db and import everything from old into new.

 

[Newman]

Yes I did! Keep getting the error.

 

[Autoeng]

Sounds like network disruptions, LAN connectivity to me Newman.

 

[Newman]

Is there somthing I could do to verifiy this? I tried Pings, but get good results. My network knowledge isn't realy good.
So, if you could give me something to look at before I call the network administrators, I'd be very happy.
Thank you!

 

[Autoeng]

Not my area of expertise (as if I have soem others!). Perhaps someone else could step in here and assist my Canadian friend.

 

[The_Doc_Man]

Usually, Access will tell you which error it detected (or at least narrow down the field.) Doesn't it tell you which error it was that zapped you? Or at least something more than "An error occurred and Access has to exit..."?

For you to get kicked out arbitrarily is strange. The first thing I would do is ask any user who connects to your DB to immediately open the "My Computer" window to look at the device hosting your DB. (In my case, the R drive.)

 

[Newman]

First, there is no error message but that it has to exit. If I click on the "Click here" link, I get lots of datas, but nothing that could help me. (It is a very large amount of datas mostly in hexa). Is there something I should be looking for in that?

Also, you said to look at the device hosting my db. It is the R drive for me too, but what do you want me to look for? If you mean "Is the drive still visible when you get kicked?" the answer is "Yes!"

 

[gmlwong]

Condition critical too!

Sorry to hear Newman...I'm having my own stress over the same messages but using;

Access 2000 Pro running on Windows 2000 as a split database.

The fe will compact but trying to compact the be doesn't work; I've tried compact/repairing it from an empty shell, from the fe mdb, can't open a new mdb and import the tables because the be must be repaired and will not...

Is it 5pm yet?@#@?$? I want to go home!?#?$! Maybe this will be a good time to take up drinking heavily@?#?!!

We did just install a new client/server application that is a database that uses common MS Access files and I'm in touch with that company to ask them about these issues.

And, I've delivered a copy of both fe and be mdb's to a disaster recovery service to see what they can do too...

Has anyone ever run into this problem where Access simply refuses to even compact/repair a database?

I would have at least expected it to return the message that says the current mdb was corrupt and that it compacted to a "db1" file to be renamed...that would have been great but that didn't happen either... IS THERE A WAY TO FORCE THIS TO HAPPEN?

Any help, greatly appreciated...! - Doc, Mr. Hartman, AutoEng, Mile, Sago...

 

[ghudson]

Have your tried the free Microsoft Jet Compact utility? Click on the link below for the version of Access you are using. For more details, search the Microsoft Knowledgebase for Jet Compact. I have had a lot of success using Jet Compact to repair a db when I thought it was corrupted and Access could not repair itself.

Access 97: Updated Version of Microsoft Jet 3.5 Available for Download

Access 2000: Jet Compact Utility Available in Download Center

Access 2002: Jet Compact Utility Available in Download Center

Also, have you tried to decompile the db?

"C:\Program Files\Microsoft Office\Office\msaccess.exe" "X:\YourDB.mdb" /decompile

Of course you should back up your db before attempting these tricks!

HTH

 

[gmlwong]

GHUDSON...!

Yes sir. I will try this for our MS Access 2000 version. Great tip and thanks in advance.

I've made a backup copy of the problem database just to help prevent any further corruption and I'm going to this site to give it a try.

I did try the normally undocumented "decompile" option (from RUN... I entered: <msaccess /decompile> but no luck because once again, since the mdb would not even compact/repair, it stopped and exited Access automatically.

Fingers are crossed so tight, I can't feel my left arm?!#?#$?!

Thanks. I'll get back soon...

 

[gmlwong]

JetCompact Utility...

Great suggestion but didn't help in this case...

Error message comes up; "Error compacting database." And goes no further. No further explanations, etc...

I've also debugged the fe copy and returned with no problems but all links to the be tables are broken because the be won't compact/repair...

I'm officially going to begin a drinking binge?@$??@! That is, after I'm able to remove the spears, daggers, and monitors stuck in my car, my chair, out my window, and maybe my head with the looks I'm getting from across the room....

I plead, "It wasn't me. It's the MS machine and Bill Gates, right?"

Any more suggestions very welcomed.

 

[jfgambit]

In answer to:

I plead, "It wasn't me. It's the MS machine and Bill Gates, right?"

See...MS Answer

 

[jfgambit]

Newman:

Does this Error happen on a specific Form or Query? I found an article from MS Knowledge about Access having a fatal error when Modules in Forms are used to supply data on the On Open or On Current event of a form. I am trying to search for the article now and will post when I find it.

 

[Newman]

Newman: Does this Error happen on a specific Form or Query...

It has happen on many forms... I am looking for which ones, since the problem may be on two or three of them.
Sorry, but couldn't understand your next sentence. (My english isn't perfect)

I am looking at a new possibilitiy now. I heard of someone who had the same problem and only thing we seems to have in common is that both of our db were created using Access97 and got changed to Access2002 latter on. gmlwong? Is it the same for you too? I'll try to change it back to A97 and run it to see if anything happens. Will give you the test's results soon.

 

[gmlwong]

Light at the end of the ...mdb!

Thanks to all respondent's for such quick and great suggestions.

For my particular issue, I contacted a local based data recovery company and they bounced it to: Brisbane, Australia's,

DataRevive at www.DataRevive.com c/o: Mr. Chris Jack.

Because my mdb would not even repair to enact any of the suggested solutions, they were able to get to the be tables, recover them, and repost my mdb for continued use.

We will naturally imploy even more measures to prevent this from happening again but it was encouraging to know that this was not something the users created but an MS Office development error...yes, Bill and company did it!

Okay, maybe not entirely MS's fault but they played a part! - Other causes include possible network issues; routing, signal delays, etc., lesser version of the MS JetEngine, not fully updated OS regardless of version,...on and on from there...

Personally, I'll be glad when we all have something else to choose from on the shelves...

 

[Newman]

Here is another problem on the same database.
I don't know if there is a link between those two problems. That's why I created another thread for it:
"ldb file for the mdw show some name twice"
Like you can see by the title, when they get connected I can see their PC# twice in the ldb file (once with the full name and once with the word "Admin"
More details on the other thread.
Thanks!

>gmlwong
I am glad to hear that you got your db back.
I was lucky enough to have backups for this database.
But I made business with PKSolutions not long ago. They charged 240US$ for a two hours work. Got the database the next morning.
Remember though that they give the database back but the problem is still not fix and that it might happen again in the near futur.
BTW... It's often MS fault. But try to prove that to your clients...
Good luck to you!

 

[Newman]

I found it!

I found it!

I don't understand why it does that, but I found out that the database get corrupted only when Miss X or Miss Y connects from home with their notebooks. Anyone else is fine but these two girls.

After many tests, we went thru a whole week with no disconnection. We thaught that the problem was solved, but it came back one week later. After many other tests, I found out that these ladies were both on vacation that week.

I asked them not to work from home and we had no more problems. Then I tried a connection at the office, but with one of their notebooks... no error. I asked the lady to give it a try at home... it crashes again.

I don't know the exact reason, but at least, I know it is not a database related problem but a network one. We transfered the case to the network administrator. The ladies will have to stay late at office to do their over-time until they find a solution for them so that they could do their over-time at home.

BTW, the names in double in the ldb file were always one of those two girls.

Thanks to everybody who tried to find a solution to my problem.

 

[jfgambit]

Great Newman...

You may want to do some reading on creating Replicas and Synchronizing Databases. It will allow the ladies to work from home and then come into the office and synchronize with the master db. Just do a Search on Microsoft on "Replicate"

Good Luck