Search results

Greetings, I believe I bumped into a contradiction. According to the official VBA docs from Microsoft here: Property Let statement https://docs.microsoft.com/en-us/office/vba/language/reference/user-interface-help/property-let-statement So I am trying to create a read-only Property that is...

Greetings Scott, Quite possibly. Anyway, I came to the conclusion that DAO objects were more fragile than ADO, and had to find a work around... which I did. I believe I only ever saw two errors in the DAO error collection in my time working on this application. Yes, SQL Server 2008 was the...

Greetings Scott, Interesting you were successfully able to raise the error over to your error handler class and grab the current error at that point out of the global DBengine. For ADO, to my knowledge there is no global ADO engine within Access. I must pass the ADO object to the error...

Greetings Frothingslosh, Of course I will compare notes/code with your version. I am thankful,

Greetings Frothingslosh, I looked back up what the sharp spot was with DAO Centralized Error Handling... Interrogation of DAO object details in the Error Handler http://www.access-programmers.co.uk/forums/showthread.php?t=246627 Ah, it was not the Err. object that was getting reset, rather...

Greetings isladogs, I have found DAO objects to be more quirky when it comes to error handling, ADO objects more robust. With DAO objects, I must have more of my error handler code repeated in the section of the code actually running the DAO object based query... trying to hand off the Err...

Coming back to this investigation fresh... I find that the ADO Disconnected Recordset VBA style code for SQL SELECT also produces an adoRS object with two errors listed in it after it successfully processes. I tried again the ADO Disconnected Recordset VBA style code for SQL UPDATE... sure...

No, sorry Galaxiom... you are missing my point. For a SQL SELECT, we were able to use the ADO Disconnected Recordset and it executes flawlessly. I tried swapping the SQL to a SQL UPDATE, and the same VBA blows up with the error cited in the OP of this thread. So I am thinking SQL SELECT is...

Greetings Galaxiom, I am angling to retain the RecordCount of the command's impact on a given table. For adoCMD objects that indeed would be the: Set recordset = command.Execute( RecordsAffected, Parameters, Options ) syntax. That syntax has the adoCMD returning a brand new adoRS object...

Greetings, Previously we got working: ADO.Command + Disconnected ADO.Recordset for SELECT https://www.access-programmers.co.uk/forums/showthread.php?t=258559&page=2#post1318234 I am trying to arrive at similar working VBA code to perform a SQL INSERT or SQL UPDATE such that I can have the...

Ah, I must have missed that point. I was concluding myself last evening that I did not see any advantages to using DAO objects over ADO... in fact, more challenging. So I will go off seeking the correct way to make manual edits to the ADO.Recordset to update the one record which is recently...

I prefer to deploy to clients sites in raw ACCDB... zero "Mac Truck" issue. So automatically close the navigation pane and ribbons, but do not more extensively prevent clients from re-opening them if they feel the need to. For consistency I Stored Proceduralized all interaction to the SQL BE...

So my Client/Server design is to SELECT to the FE DB to display in a totally disconnected FE interface. There is a Requery button on each Multiple Items form to refresh the data completely by rerunning the Stored Procedure, purge and refresh the FE Temp Table. So when Updates are made to the...

I have not rolled out a production application with the ADO solution... researching options. For production Access Client/Server applications, those make use of Access FE temp tables records are downloaded into, the Access Continuous Forms are bound to via a Access FE QueryDef. I am...

1) Security risk of people tinkering opening the linked tables through the Access UI, changing things ad-hock. 2) Speed. Using exclusively Stored Procedures for SQL BE DB and disconnected recordsets in the Access FE DB delivers lighting fast performance. Just the one downside is Access FE DB...

I found this page describing a non-SQL way to make edits to a DAO.Recordset object: "How to: Modify an Existing Record in a DAO Recordset" https://docs.microsoft.com/en-us/previous-versions/office/developer/office-2007/bb243797(v=office.12) Something along those lines is what I am seeking...

In order to invoke the Stored Procedure on the SQL BE DB. But I do not use Linked Tables at all. The SQL Stored Procedures on the SQL BE DB frequently join many tables within the BE DB into a concise single record set. Those are downloaded to the Access FE DB for display, and no long lasting...

This is prototyping / experimental code, which I am treating an Access table as if it were a SQL BE DB table. In production use, yes I would be using a Pass-Through query to execute a Stored Procedure on the SQL BE DB, and and and... Keeping it very simplistic for my forum question. The goal...

A while ago we were having a discussion about having a ADO objects feed data into an Access Multiple Items form. Today I discovered one can do almost exactly the same with a DAO.Recordset based on DAO.QueryDef. Link to our prior Access Continuous Form fed via ADO objects: "Example of ADO...

Thanks sonic8, that gave me enough of a memory jog. I arrived at this working syntax: Dim adoCMD As Object Dim adoRS As Object 'Define attachment to database table specifics and execute commands via With block Set adoCMD = CreateObject("ADODB.Command") With adoCMD...