I am new to Microsoft Visual Basic and I'm trying to run an Excel macro built to parse an internet explorer htlml file. However I keep getting the following error "Run-time error '91': Object variable or With block variable not set. When I run microsoft visual basic I see the following highlighted in yellow:
Set nameElement = anElement.Children.Item(0).Children.Item(1).Children.Item(1).Children.Item(1).Children.Item(0).Children.Item(1)
Any suggestions on how to correct this error and get the macro up and running?
Related
I've been using an Excel where a UserForm shows up as the Excel opens.
Now, for a reason it doesn't even show up anymore, it just gives me a run-time error with a code. The weirdest thing is, that there were no changes in the code, it's been working without any problem.
Here is the error:
"Run-time error '-2147467259 (80004005)":
[Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key Temporary (volatile) Ace DSN for process 0x1a88 Thread 0x3450 DBC 0x2a5d24b4
Jet'.
Please, help me figure it out.
Thanks in advance!
[The Yellow Line is where error occurs][1]
Help me debug and know possible cause of error '1004' in vba
[1]: https://i.stack.imgur.com/fHOwG.png
This is similar to a question that I've asked yesterday, but I've managed to find a fair bit more information: enough to warrant a new question, I feel.
My office has recently moved to Windows 7 along with Office 2013 - with the except of Access which has stayed as 2003.
Access works absolutely fine except when I try to automate Excel. This is a feature of nearly all my applications.
When I load an old project, the reference is automatically updated to "Microsoft Excel 15.0 Object Library" - it is held as an EXE file in Program Files (x86). Note: it does not say the reference is missing.
When I try to run any code which uses early binding, it fails with the following error message: "Error in loading DLL"
I've since tried late binding by doing the following:
Dim app As Object
Dim wb As Object
Set app = CreateObject("Excel.Application")
app.Visible = True
Set wb = app.Workbooks.Add
This creates the Application, it becomes visible, a Workbook is added, but then I get the following error: "Run-time error '1004':
Application-definted or object-defined error"
If I try to access VBA in the new Workbook I get the following error: "An error occurred initializing the VBA libraries (1004)" The Workbook is loaded in "Compatibility Mode"
The above leads me to believe that the 2 applications may not be compatable, but the following is worth considering:
If I try to use early binding I don't get the Intellisense drop-downs but words like Workbook and Worksheet do auto-capitalise themselves as you would normally expect them to. The code won't compile at all if I don't have the reference set, but it does compile - and throw and error - when it is. I've since tried Word 2013 - who's Object Reference is an OLB file rather than EXE - and I get the full Intellisense features I would except, but it still throws the same error when trying to run.
In a nut shell, does anyone know if I stand any chance of having the 2 work together?
Thanks
I am seeing an Error 438 in an application which has until this point been run successfully without error for more than 2 years. Debug shows that it fails on a fairly inoccuous line:
With gVarWorkSheet.ListView1
The workbook has not changed since previous successful runs. Is there anything in the installation of Excel or on the Windows XP PC in general that could have changed that would cause this?
When configuring an Excel Data Flow Component (Source) using the AccessMode of OpenRowset from Variable and setting the correct variable, I get the following error when trying to configure the shape/preview the data:
TITLE: Microsoft Visual Studio
Exception from HRESULT: 0xC02020E8
Error at Merge Files [Excel Source [2]]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E37.
Error at Merge Files [Excel Source [2]]: Opening a rowset for "[WORKSHEET]" failed. Check that the object exists in the database.
I have checked that variable name is correctly set to the name of a valid worksheet.
How do I fix this error?
You need to append a dollar sign on the end of the worksheet variable, e.g. WORKSHEET$