Search results

And I suppose the environment that Application.Eval() creates is not suitable to to succeed at making the LOC generic? Did you try?

You would need to insure that the proper form / subform has focus. See... How to SetFocus to a specific control on a Subform of a Form http://www.access-programmers.co.uk/forums/showthread.php?t=221705#post1132324 Then use the SendKeys capability: Minimize Ribbon...

I put a Watch on the CurrentProject object and compared the two connection subobjects. On A2007, Connection has V12 attribute things whereas AccessConnection has V10 attribute things. I think I will stick with using Connection. The test application worked the same either way. I found this...

I have one long form with a couple of subform controls on it that sometimes does this nonsense. In my case, if top fields are blank and only fields lower down the form have values, then Access jumps the UI to be focused on fields which actually had data populated to them. It is a bit annoying...

Galaxiom, your slight of hands is indeed intreaguing... I had no idea that I could load up an adoCMD object and then create an adoRS object, feed it the adoCMD object having the adoRS object actually execute what had been loaded into the adoCMD object in the first place. Please see the updated...

Previously I had been running Access applications through paces "torture testing" and had come up with three DoEvents being required to completely flush the input queue of all Esc / Cancel requests. Abridged example: Private Sub btnClose_Click() 'Flush keystrokes out of the buffer so that...

I am glad to see you found a work-around for your challenge, Foe. Occasionally I have run into "Access not responding" nonsense. In such cases I have managed to work around it that the code was loop based and did not interact with the UI at all. At the end of the loop code before it re-runs the...

I was not trying to provide update capabilities. Rather read-only view of multiple qualifying records. So, how are you able to achieve such for read-only display of records? Or do you run your queries through ADO.Recordset objects and not ADO.Command objects? Please post some example code.

Oh... so does that means you do not use ADO.Command objects to execute Stored Procedures, resulting in an ADO.Recordset, which you then bind to a Multiple Items / Continuous style form?

All right, one error at a time, I have arrived here with my prototype code: [CODE]Private Sub Form_Open(Cancel As Integer) Dim adoCMD As Object Dim strSQL As String strSQL = "SELECT [t].[pid],[t].

Thanks Galaxiom. Might you also have in your bag of tricks how to obtain an exact copy of an ADO.Recordset object WITHOUT stooping to interpretive brute-force code? I see that point as one challenge with efficiently utilizing Fabricated ADO.Recordset objects and binding them to Forms...

Perhaps the name has changed over the years to what I see in A2007? I know of no way to obtain a Multiple Items / Continuous form otherwise. Specifically the Detail section I know of no manual way to obtain on a blank form.

All right, this looks like it has possibilities... I was able to get an adoRS object to populate a Multiple Items Form. I cannot get the form to open at the last height I had it at while in form edit mode. In general, I see potential for this concept. I had to submit the query directly with...

A post I refer to for driving Excel from Access: How to drive Excel with VBA (Access) in order to transfer values into spreadsheet http://www.access-programmers.co.uk/forums/showthread.php?t=233104#post1190025 And I have an ADO.Recordset working from Access to Excel: Public Sub...

Create \ More Forms button \ Multiple Items Simple Add/Edit record forms are simple to create as unbound forms and I use ADO.Command objects in the DB class when working with such forms. They only deal with one record, thus are simple. Until now, I have used temp tables and have bound Multiple...

How would you populate a Multiple Items form without having it bound, at least to the ADO.Recordset object? I do not care for editable Multiple Items forms. No free wheeling "spreadsheet database" applications! NO! NO! ;) So Galaxiom, you have had success with having an ADO.Recordset object be...

In general it is very bad to tie other business logic to the value of autonumber fields. The autonumber fields are unique to the application, but not guaranteed to remain the same forever... like through export/import or DB compact operations. You should develop your own mechanism / code for...

In my mind, Forms and Reports were hard coded to only work with DAO objects. It is nice that some functionality is still in Access from when MS was on that "Pro ADO" kick a few years ago. You have me intrigued to attempt to execute a query against a SQL BE DB (ADO.Command object returning...

I stepped through the code execution... pretty slick what you have accomplished thus far. I thought surly one had to use DAO objects when bound to forms. So what about creating the adoRS object at Form level. When the form opens, do the: Set Me.Recordset = rs LOC. Then in an AddRecord button...

Here is a link to just such a module solution... ADO Constants for use with Late Binding ActiveX Data Objects 2.8 Library http://www.access-programmers.co.uk/forums/showthread.php?t=243088