Microsoft Access Developer Center

Table Design

Query Design

Form Design

Form Tips and Mistakes

Module VBA to Forms and Controls

Form Navigation Caption

Using a RecordsetClone

Synchronize Two Subforms

Multiple OpenArgs Values

Late Bind Tab Subforms

Subform Reference to Control Rather than Field

Tab Page Reference

Shortcut Keys


Combo Box Top Tips

Properties and Validation

Select First Item

Cascading Combo Boxes

Zip, City, State AutoFill

Report Design

Suppressing Page Headers and Footers on the First Page of Your Report

Add the NoData Event

Annual Monthly Crosstab Columns

Design Environment

Adding Buttons to the Quick Access Toolbar

Collapsing the Office Ribbon for more space

VBA Programming

Basics: Forms and Controls

Using Nz() to Handle Nulls

Avoiding Exits in the Body of a Procedure

Shortcut Debugging Keys

Setting Module Options

Math Rounding Issues

Rename a File or Folder

Avoid DoEvents in Loops

Age Calculations

Weekday Math

Sending Emails with DoCmd.SendObject

Source Code Library

Microsoft Access Modules Library

Microsoft Access Modules

VBA Error Handling

Error Handling and Debugging Techniques

Error Number and Description Reference

Basic Error Handling

Pinpointing the Error Line

Performance Tips

Linked Database

Subdatasheet Name

Visual SourceSafe

Deployment

Runtime Downloads

Simulating Runtime

Prevent Close Box

Disable Design Changes

Broken References

Remote Desktop Connection Setup

Terminal Services and RemoteApp Deployment

Reboot Remote Desktop

Missing Package & Deployment Wizard

Avoid Program Files Folder

Microsoft Access Front-End Deployment

System Admin

Disaster Recovery Plan

Compact Database

Compact on Close

Database Corruption

Class Not Registered Run-time Error -2147221164

Inconsistent Compile Error

Decompile Database

Bad DLL Calling Convention

Error 3045: Could Not Use

Converting ACCDB to MDB

SQL Server Upsizing

Microsoft Access to SQL Server Upsizing Center

Microsoft Access to SQL Server Upsizing Center

When and How to Upsize Access to SQL Server

SQL Server Express Versions and Downloads

Cloud and Azure

Cloud Implications

MS Access and SQL Azure

Deploying MS Access Linked to SQL Azure

Visual Studio LightSwitch

LightSwitch Introduction

Comparison Matrix

Additional Resources

Microsoft Access Help

MS Access Developer Programming

More Microsoft Access Tips

Technical Papers

Microsoft Access Tools

Connect with Us

Email NewsletterEmail Newsletter

FMS Development Team BlogDeveloper Team Blog

Facebook PageFacebook (Feed)

Twitter with FMSTwitter

FMS Support SiteSupport Forum

 

Verify Linked Tables in Your Microsoft Access Application

Provided by: FMS Development Team

Microsoft Access Source Code LibraryEver had a user move a backend Microsoft Access database or delete it?

Here is a routine you can use to ensure that the linked table actually exists in the location specified using ADOX. You should be able to cut and paste everything from the "Begin Function" line to the "End Example" line into a new module and have it work for you.

This comes from Total Visual SourceBook's modADOJetADOX module. There's also an equivalent set of code to use DAO in CJetLinkedTables and CJetDatabase classes.

Required References: ADO Extensions for Data Definition Language and Security (ADOX)

' This Reference is seen in the References Dialog as "Microsoft ADO Ext. 2.x For DDL and Security"
'************ Begin Function Code ************
Public Function ADOXTestLinkedTable(cnnConnection As ADODB.Connection, strTable As String) As Boolean
 ' Comments : Tests the specified linked table to see if its link is valid
  ' Params   : cnnConnection - open ADODB connection to the Jet Database
  '            strTable - name of the table to test
  ' Returns  : True if the link is valid, False otherwise
  ' Source   : Total Visual SourceBook
   Dim catTmp As New ADOX.Catalog
  Dim tblTmp As New ADOX.Table
 Dim strTmp As String
 Dim lngSaveErr As Long

 On Error GoTo PROC_ERR

 ' Open the catalog by setting its ActiveConnection property
 catTmp.ActiveConnection = cnnConnection

 ' Set a pointer to the table
 Set tblTmp = catTmp.Tables(strTable)

 If tblTmp.Properties("Jet OLEDB:Create Link") = True Then
    ' It is a linked table so try to open it by getting the
    ' name property of one it its fields. If the table's link
    ' is not valid (for example, the database it is pointing to
    ' is moved, deleted, or renamed) this call will fail. We
    ' Disable error handling to handle a potential failure.
    On Error Resume Next
    strTmp = tblTmp.Columns(0).Name

    ' Save the error number
    lngSaveErr = Err.Number

    ' Re-enable error handling
    On Error GoTo PROC_ERR

    ' If the save error number is not 0, an error occurred
    ' and we can assume that the link is invalid
    ADOXTestLinkedTable = (lngSaveErr = 0)
  End If

  ' Close the catalog to release resources
  Set catTmp = Nothing

PROC_EXIT:
 Exit Function

PROC_ERR:
 MsgBox "Error: " & Err.Number & ". " & Err.Description, , "ADOXTestLinkedTable"
 Resume PROC_EXIT

End Function
'************ End Function Code ************
'************ Begin Example Code ************
' To call the above function, all you need to do is open a connection to the database.

  Dim cn As ADODB.Connection
  Set cn = New ADODB.Connection

  ' Open the connection
  With cn
    .CursorLocation = adUseServer
   .Open "Provider=Microsoft.Jet.OLEDB.4.0;" & _
    "Data Source=C:\Northwind.mdb"
  End With

  'Example code for ADOXTestLinkedTable
  Debug.Print ADOXTestLinkedTable(cn, "Categories")
'************ End Example Code ************"