Search results

All of that is valid criticism. I didn't post the entire CoPilot answer as I knew that significant parts of it were incorrect. However, I failed to state that in my post for which I apologise unreservedly. I did state that your function appeared to always give the right answer in my own tests...

As stated above, both the code in post #2 and that in post #7 appear to give correct results in my tests However, here is the CoPilot critique of Philipp's simple function from post #7 EDIT: There are a lot of incorrect statements in the CoPilot summary above - See @posts #11 & #13 for details...

The problem is that it doesn't actually check whether the value is within the large integer (BigInt) range: -9223372036854775808 to 9223372036854775807 (-2^63 to 2^63-1). For example -92233720368547758080 is wrongly marked as a large integer using your code Both the CoPilot code in post #2 and...

Is your data in SQL Server? If so the issue may be with a boolean field

Rather than check the installation folder, I would just test for Office bitness using the Win64 compilation constant Win64 is True when VBA is running in a 64-bit Office environment. It is False when running in 32-bit Office, even if the operating system itself is 64-bit. So I just use this...

Sorry Duane. Access automatically used the name that @Imb gave to the database.

How about supplying an ACCDB starter app which detects the Office bitness then starts the required ACCDE file. Will that work in Runtime? If not, then make the client manage the situation.

Out of interest, why do you want themes to be disabled?

Its in Access Options | Current Database | Applications Options - exactly the same place as in my screenshot in post #13. Of course even if that option is ticked (default setting), themes won't have any effect on .mdb files

My first impression is of how difficult this interface is to navigate. I don't speak Dutch which made things harder but I found the interface far from intuitive. Within a few minutes I had a screen littered with multiple instances of the same form, all looking very similar, with each having to...

If anyone wants to try out @Imb's example file from post #24 in 64-bit Access, I have recompiled it in both MDE and ACCDE formats. Both should work in 64-bit Access from A2010 onwards. NOTE: As with the original version, both files below contain one VERY old API based on msoe.dll and dating...

I assume you are referring to the ribbon which was Microsoft's attempt to make menu items appear when relevant to the current task e.g. Form Design. Prior to that there were many features that were rarely if ever used as most developers didn't know they existed! Unfortunately the ribbon wasn't...

Forward compatibility isn’t normally a problem. Backward compatibility may also be OK as long as no newer features are used

It might be worth repeating the tests with a larger dataset as that may affect the overall efficiency. My very simple test database is attached

My last reply was posted within a few seconds of yours. With that data change I get the correct output for all 3 queries For info, the original query is still the fastest. Here are the times running each query 10 times on a loop

I used your data from post #1 where both records where PricesQuantity=10 had the same date 2016/03/01. In your post #13, the two records have different dates with record 1743 being 2024/11/05 It would have been easier both for you and us if you had uploaded a sample database with the data and...

I agree that the original solution in post #2 is faster. What I was saying was that using your data, the 2 solutions give different results The post #2 solution has 2 records for PricesQuantity = 10 though at the moment I'm not sure why Is that really what you are expecting? If so, that's fine.

The subquery in post #2 was incorrect. It gives two records for PricesQuantity = 10 & a total of 8 records The version suggested by @DaveMD is both much simpler and appears to be correct with only 7 records

Yes i know. I have his free scanner but not his commercial auto converter. in this case there are 15 modules with APIs to check / convert.

I wasn't offended. I meant its entirely your choice. The handling of themes and the range of button styles was significantly improved with version 2010. I'm using 365