Home |
Search |
Today's Posts |
|
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
On Dec 1, 5:45*pm, "JLGWhiz" wrote:
As best I can tell, different folks worked on different applications and each individual tailored the VBA software to their specific application. You could just as easily wonder why they change the code from release to release in Excel VBA. *Software engineers seem to have this feeling of ownership about their work assignments and they don't like to give someone else credit for any of their work, so they try to make everything look like it is better by making it different. *But the real answer is probably that they were too lazy to research to see if a procedure already existed for I think I figured it out. Evidently Access VBA already contains Recordset and Connection objects that are different from ActiveX Data Objects. When I changed the declaration from Dim rst as Recordset to Dim rst as ADODB.Recordset, the syntax changed to what I expected it to be. So in other words there are 2 completely different Recordset,etc objects. |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
syntax error in VBA in query from Access | Excel Discussion (Misc queries) | |||
Syntax to address ThisWorkbook.BuiltinDocumentProperties via Access Automation? | Excel Discussion (Misc queries) | |||
Excel VB - WHERE syntax error in Access web query. | Excel Programming | |||
SQL syntax in VBA for Access | Excel Programming | |||
Microsoft][ODBC SQL Server Driver]Syntax error or access violation | Excel Discussion (Misc queries) |