Run Time Error 3000 with Reserved Error -1517

[CptCrusty1]

I have a database that has numerous other databases linked to it. Each user (around 200) has their own front end which is linked to it. Every now and again we get an error:

"RUN TIME ERROR '3000':
Reserved error (-1517);there is no message for this error."

When ever we get this error, we have to kick all users out, delete all the linked tables in their databases, and relink to the master database. It usually takes about 1/2 a day to do all this.

Does anyone know of a possible cause?


I live to work and I work to live.

 

[MePenguin]

Just got this error when trying to open an append query from VBA, the code hangs on the line:

DoCmd.OpenQuery "QCountsheetSamplesToTSample", acViewNormal

as yet I have no idea why, did you figure it out?

Regards,

Phil

---------------
Pass me the ether.

 

[MePenguin]

OK, seemed to be caused by corrupt something in the database... maybe links to tables in backend, according to other posts. Compact & repair frontend and backend solved it for me.



Phil

---------------
Pass me the ether.

 

[CptCrusty1]

Doing a compact & Repair on the front end and back end is a workeable solution for us, however, since we have well over 100 users, we have to have the IT junkies kick them all out. Once they are all out, we have to quickly rename the master (backend) db so they can't find it, otherwise, some yahoo poweruser wannabe will get into the db thinking they know what they're doing (and we do?? LOL). Anyway. This happens once a week and is guaranteed to take 4 hours to fix either way. I have got to find another solution.

Any suggestions are welcome (other than tactical nuclear weapons).

Crusty

I live to work and I work to live.

 

[MePenguin]

Not sure of any way around that... I use the flagging system from faq705-2852 by billpower to compact and repair frontends on quit when they get too big - doesn't solve your backend problem, but maybe useful if the f/e is causing the trouble?

Example follows:

Dim BugsCEPSize, BugsCEPMaxSize As Variant
    'get current size
    BugsCEPSize = FileLen(CurrentDb.Name)
    'get max permissable size from table
    BugsCEPMaxSize = DLookup("ValueNum", "TSettings", "Setting='MaxSizeFE'")
    
    'Set the compactonclose flag and warn user if going to compact
    If BugsCEPSize > BugsCEPMaxSize Then
        msg = "blah blah..."
        response = MsgBox(msg, vbInformation + vbYesNo, "Bugs needs compacting")
        If response = vbYes Then
            'Note following lines taken from faq705-2852 by billpower on tek-tips.com
            Application.SetOption ("Auto Compact"), 1  'compact app
        Else
            Application.SetOption ("Auto Compact"), 0   'don’t compact app
        End If
    Else
        Application.SetOption ("Auto Compact"), 0   'no don’t compact app
    End If

Or you could monitor the yahoos and find out how they solve it all by pure idiotic ingenuity

Regards,

Phil

---------------
Pass me the ether.

 

[CptCrusty1]

Phil,

Its the backend the crashes. We usually get the message "not a recognized database format. Do a compact and repair... yadda yadda." At that point we have to shut everyone down.

We should probably put something in place to kill everyone's connections to the Backend and the compact and repair the backend nightly.

I live to work and I work to live.