Search results

For a generic lookup the class will still work, you will need to provide more information. With AnyTableClass .QueryToOpen = "Your Named Query" .ParmName = "Your ID lookup Parameter" .LookupID = YourKeyValue Description = nz(.ColumnFromRS(1)) Location = nz(.ColumnFromRS(2)) End With Option...

I agree this would be over kill for one off lookup of a single column. The OP indicated repeated lookups for multiple columns and the possibility of keeping a recordset open to do it. Assuming this is part of a single function call, initiating the class once and using it repeatedly for each...

Simpler and faster then a bunch of dLookups. Option Compare Database Option Explicit ' Sample Class to search recordset and return values Private Type MyTableType qd As DAO.QueryDef rs As DAO.Recordset End Type Private This As MyTableType Private Sub Class_Initialize() ' Do...

Any server backend support by Access will work, but may be slower than a "Access" BE depending on how the FE was coded i.e. opening a form linked to a table without a filter. The corruption issue on WAN is only with an "Access" BE.

If you are filling variables from table columns like the following Description = MyTableDesc(LookUpID) Location= MyTableLocation(LookUpID) .. SomeOtherField = MyTableSomeOtherField(LookUpID) Consider using a class to fill and return values from your query. With New MyTableClass .LookupID =...

Have you confirmed the RegKey exists on the computers with the problem?

New Outlook does NOT support COM automation. You will need to revert to old Outlook for use something else like Microsoft Graph. Your code snip is using late binding, so checking "Microsoft Outlook 16.0 Object Library" does nothing for your code. It may also be the source of your error if using...

Easy to test. Class1 Private Sub Class_Initialize() Debug.Print "Class_Initialize" End Sub Private Sub Class_Terminate() Debug.Print "Class_Terminate" End Sub Module1 Public Sub Test() With New Class1 Debug.Print "Module1 Test" End With End Sub Normal run test...

I was at work. One of office managers pulled up the new feed after the 1st hit. It was very strange how quite it was outside with no air traffic overhead.

Add 2 more test where the recordset is not recreated in the loop, required 10,000 searches to see a difference. Note: it the previous test I neglected to user dbOpenTable on the seek recordset, which is requited. Select time: 15 Seconds, Found: 1000 Select Parm time: 13 Seconds, Found: 1000...

That 1st query is used to fill the array with part numbers to search and is not included in the timer.

Seek works with a linked Access table. tblParts in my example is linked.

At 1st I thought the select would be faster so I did a test on a large table with 300000 + records and seek was faster in this test. TestSelectVSeek Time in seconds Select time: 18 Select Parm time: 15 Seek time: 14 Public Sub TestSelectVSeek() On Error Resume Next Dim...

No reason you can't build the query testing multiple comparisons by also testing a 2nd parameter for which one will be true. Where ([FieldToTest] > [Param1] and [Param2]=">") or ([FieldToTest] < [Param1] and [Param2]="<")

Error reports from users are notoriously un-reliable. Years ago I added logging of all trapped errors. Now I can check the log whenever there is a "CRASH" making it much easer to diagnose what the use(s) were doing before the problem.

I agree with MarkK. If you can, open the tables referenced by the form, sort each column high to low, low to high noting any null values.

It is documented by Microsoft, but I don't have a link. I am using an archive BE and have seen the problem, you can setup a transaction and process the move between BE dbs. without any warning including failures.

You can write the code to export all objects to text. Make table with a list of all objects in the current Access. Loop over a record set exporting the objects. Copy the table to the new MDB in Access 2003 Loop over a record set importing the objects. You could possibly use a version control...

The only time I open a naked query for a user is for a quick copy and paste and then only in read-only mode.