How to gracefully handle errors generated when opening a form with linked data? (1 Viewer)

[cricketbird]

When I open an Access DB, it it set to open a Welcome form which runs some code in the 'Form_Open' event. However, if the backend is offline, the 'Form_Open' code will generate an error. In my error handling to the 'Form_Open' function, I have it set to open the "Settings" form where the user can re-link the tables. The Settings window does indeed open as intended, but the Welcome form immediately opens again, hiding the "Settings" window and confusing my users. I think this is because the Welcome form's subsequent 'Form_Load' function has (otherwise necessary) steps that draw the focus back to Form A.

Is there a way to have Form_Open return an error that the Form_Load can use. e.g. if iserror(Form_Open) then do X, else do Y?

Or, what would the best practice be for code that needs to run on the Welcome form that requires access to the backend but also gracefully handles the situation of allowing the user to relink the backend when needed and then resuming running?

 

[bastanu]

Try to open the Settings form as a modal instead so it will wait until the user relinks the BE before passing control back to the calling sub.

Cheers,

 

[MajP]

See if this relinker helps

Setting Database default paths

It really wasn't a big deal. I don't expect to be "spoon fed" with this stuff. Sometimes you just have to get in there and sort it! It was the modules that got me. I didn't realise until I got into the code that they were required. Not to worry though. It's a good piece of code.

www.access-programmers.co.uk

 

[Pat Hartman]

To avoid this type of issue, I have special purpose code in the opening form of an application which is always unbound. The first form starts by checking to see if two of the tables of the application are available. Pick any one or more or even all tables to check. If there are no errors, the login form opens and the login proceeds. Otherwise, the relink form is opened. Simpler all around than starting with a bound form and trying to recover from an error.

Here is the simplest version of the code I could find.

Private Sub Form_Activate()

    On Error GoTo ErrProc
    If DCount("*", "tblCustomers") >= 0 Then
        DoCmd.OpenForm "frmLogin", , , , , , Me.Name
    Else
        DoCmd.OpenForm "frmRelinkJetORACEtables", , , , , , Me.Name
    End If
    Me.Visible = False
    
ExitProc:
    Exit Sub
ErrProc:
    Select Case Err.Number
        Case 3044   ''' table not found
            DoCmd.OpenForm "frmRelinkJetORACEtables", , , , , , Me.Name
        Case Else
            MsgBox Err.Number & " -- " & Err.Description
    End Select
End Sub

 

[apr pillai]

You have not shared the Form_Open() Event Procedure or the Error handling segment to take a look at them. Anyway, assuming that the following blog post, that explains what to do in such eventualities, is a solution for MDB BE file on LAN, hope it will help you to sort out your issue yourself: https://www.msaccesstips.com/2008/09/lost-links-of-external-tables.html?m=1

 

[cricketbird]

Try to open the Settings form as a modal instead so it will wait until the user relinks the BE before passing control back to the calling sub.

Cheers,

I tried this first as the simplest solution, and it worked beautifully! Thank you!

 

[cricketbird]

Thanks everyone - it wasn't re-linking that was the problem. I ended up moving everything to Form_Open and changing the "settings" form to modal, and that did the trick.