<div>
Error 429 means that VBA can't create an object. One of the reasons is that the object you are trying to create isn't compatible with the environment you are trying to create it in; e.g. trying to create a 32 bit object while running in a 64 bit environment. VBA references objects in the order that they appear in the References list. Make sure that the first object library which contains Excel has the same number of bits (32 vs 64) as the number of bits in Access. As a debugging method, see if the code snippet runs using a new, empty database, adding the minimum number of references needed to make the code run. If it runs in this clean environment, compare the ticked references in the two projects to see if different libraries are being referenced or in different orders. Keep in mind that switching which object libraries are referenced and the order of references may fix your issue while causing a side effect in the remainder of your code. If the object reference list doesn't appear to be the issue, try the code snippet on another computer. If it works there, then again compare the object libraries between the two computers to see if a difference is the source of your issue.
</div>

Senior Developer

ste5an

<div>
I need to guess, this just snippet of a large method? Are you sure, that is the offending part? 
 
I would start by refactoring this. So that we can be sure. E.g. 
 

<pre><code class="code-10 nolinks" id="code-20-43295857-1">Option Compare Database
Option Explicit

Public Const NO_ERROR As Long = 0 ' Declare once.

Public Sub Test()

 'Step 110-Prepare MS Excel Application Common Variables.
 Dim DebugErrorNumber110 As Integer
 DebugErrorNumber110 = 0
 Dim EmptyMSExcelFileFlag_110 As Boolean
 EmptyMSExcelFileFlag_110 = False
 Dim MSExcelApplication_110 As Object
 On Error Resume Next
 Set MSExcelApplication_110 = GetObject(, &quot;Excel.Application&quot;)
 DebugErrorNumber110 = Err.Number
 If Err.Number &lt;&gt; 0 Then
 Set MSExcelApplication_110 = CreateObject(&quot;Excel.Application&quot;)
 Debug.Print Err.Number, Err.Description
 EmptyMSExcelFileFlag_110 = True
' GoTo STEP_120 'Step 120-Define MS Excel Workbook / Worksheet Import Variables.
 Else
' GoTo STEP_120 'Step 120-Define MS Excel Workbook / Worksheet Import Variables.
 End If

End Sub

Public Sub Refactored()

 Dim MSExcelApplication_110 As Object

 Set MSExcelApplication_110 = ExcelApplication
 If Not MSExcelApplication_110 Is Nothing Then
' GoTo STEP_120 'Step 120-Define MS Excel Workbook / Worksheet Import Variables.
 End If

End Sub

Private Function ExcelApplication() As Object
 
 On Local Error Resume Next

 Err.Clear
 Set ExcelApplication = GetObject(, &quot;Excel.Application&quot;)
 If Err.Number &lt;&gt; NO_ERROR Then
 Err.Clear
 Set ExcelApplication = CreateObject(&quot;Excel.Application&quot;)
 If Err.Number &lt;&gt; NO_ERROR Then
 MsgBox &quot;Cannot retrieve or create Excel instance.&quot; &amp; vbCrLf &amp; vbCrLf &amp; &quot;[&quot; &amp; Err.Number &amp; &quot;] &quot; &amp; Err.Description, vbExclamation
 End If
 End If

End Function
</code></pre>
And I also would get rid of those GoTo's &nbsp;They are in almost every case not necessary and better implemented as functions and appropriate If-statements. Also some of your control Boolean are normally not needed, when using appropriate If's instead.
</div>

System Architect

Bob Collison

<div>
Hi Experts, I have used Fabrice's suggestion and it appears to have solved the problem. &nbsp;I have to cleanup the code and complete testing but all looks excellent. &nbsp;I'll update the question when testing is complete. I have know idea why it works and my code doesn't. I would like an answer to the questions concerning References and how to determine if the Access / Office is 32 or 64 Bit. Thanks, Bob C.
</div>

<div>
I suggest that you focus on the strict necessary, noyhing else, nothing more. Any VBA functionality must focus on the nominal execution flow. If errors (exceptions) happen, leave that task to the error handlers, so you code isn't polluted with bunch tedious and unreadable error number checking. References arn't an issue since you're using a late binding instantiation strategy. As for what caused the error, honestly no clue. But, by seeing the code's quality, I suspect an old history bug that remained silent untill today.
</div>

<div>
@Bob: It did almost exactly the same, what Fabrice did. 
 
The only differences where: 
 
- I kept your instantiation logic alive. 
- I did not reraised an error. Either I handle it or I don't catch it. Reraising in VBA should be done in the most seldom cases.
</div>

<div>
Hi Experts, Thanks for the updates. Gary Thanks for the info to find the Access Version. &nbsp;I have the 32 Bit which I understand is still much more common than the 64 Bit. You are right about the Excel Object Library being missing. &nbsp;I checked my documentation and sure enough I had it as requiring specification. &nbsp;I will add it back in. Fabrice / ste5an Thanks for the additional insight. Thanks. Bob C.
</div>

<div>
<div class="content wysiwyg-content fr-view">
Hi Experts, I have the following code that used to work perfectly. No I get Error 429. 'Step 110-Prepare MS Excel Application Common Variables. Dim DebugErrorNumber110 As Integer DebugErrorNumber110 = 0 Dim EmptyMSExcelFileFlag_110 As Boolean EmptyMSExcelFileFlag_110 = False Dim MSExcelApplication_110 As Object On Error Resume Next Set MSExcelApplication_110 = GetObject(, "Excel.Application") DebugErrorNumber110 = Err.Number If Err.Number &lt;&gt; 0 Then &nbsp; &nbsp;Set MSExcelApplication_110 = CreateObject("Excel.Application") &nbsp; &nbsp;EmptyMSExcelFileFlag_110 = True &nbsp; &nbsp;GoTo STEP_120 &nbsp; 'Step 120-Define MS Excel Workbook / Worksheet Import Variables. Else &nbsp; &nbsp;GoTo STEP_120 &nbsp; 'Step 120-Define MS Excel Workbook / Worksheet Import Variables. End If Could you please let me know if there is something obviously wrong with this code? Thanks, Bob C.
</div>
</div>

Hi Experts,
I have the following code that used to work perfectly.
No I get Error 429.
'Step 110-Prepare MS Excel Application Common Variables.
Dim DebugErrorNumber110 As Integer
DebugErrorNumber110 = 0
Dim EmptyMSExcelFileFlag_110 As Boolean
EmptyMSExcelFileFlag_110 = False
Dim MSExcelApplication_110 As Object
On Error Resume Next
Set MSExcelApplication_110 = GetObject(, "Excel.Application")
DebugErrorNumber110 = Err.Number
If Err.Number <> 0 Then
   Set MSExcelApplication_110 = CreateObject("Excel.Application")
   EmptyMSExcelFileFlag_110 = True
   GoTo STEP_120   'Step 120-Define MS Excel Workbook / Worksheet Import Variables.
Else
   GoTo STEP_120   'Step 120-Define MS Excel Workbook / Worksheet Import Variables.
End If
Could you please let me know if there is something obviously wrong with this code?
Thanks,
Bob C.

Problem With Access 2016 CreateObject for Excel

Visual Basic for Applications (VBA) enables building user-defined functions (UDFs), automating processes and accessing Windows API and other low-level functionality through dynamic-link libraries (DLLs). VBA is closely related to Visual Basic and uses the Visual Basic Runtime Library, but it can normally only run code within a host application rather than as a standalone program. It can, however, be used to control one application from another via OLE Automation. VBA is built into most Microsoft Office applications.