Recent content by Josef P.

Look at param name. With CurrentDb.QueryDefs("YourQuery") Debug.Print .Parameters(0).Name ' => [Tempvars("dtFrom")] or Tempvars("dtFrom") End With => if [...] prm.Value = Eval(TrimChar(prm.Name, "[]")) Public Function TrimChar(ByVal TextToTrim As String, ByVal CharsToRemove As String)...

I would classify this as a floating point issue in Jet/ACE. Range of Single: 1.401298E-45 to 3,402823E38; -3,402823E38 to -1.401298E-45 Pay attention to the decimals. ? CSng(1.00000004749745E-03) = CDbl(0.001) => True but: ? CDbl(CSng(1.00000004749745E-03)) = CDbl(0.001) => False Round is...

For now, I’ll continue using the .NET COM DLL for my testing. Thanks to everyone contributing their thoughts. Short background information: This is an attempt to read all declarations from the project references and merge them with the declarations in the VBProject. The purpose is to verify...

I assume that too. The problem is likely that the returned "object" is not a valid VBA object (missing IDispatch interface?).

Thanks for the reference to TypeLibVwr, I didn't know it yet. The code of the .net-dll is not complex. I would just like to know whether it is possible to use the API in VBA with a manageable amount of effort. In the Excel example, every method within pptlib/ITypeLib is called via API. API...

A little challenge for Windows API enthusiasts and COM/VBA experts: Has anyone ever successfully read type library information (e.g., class and method names) from a COM DLL in VBA, using Windows APIs like LoadTypeLibEx? My attempts to use it without too much effort were unsuccessful. I came...

Now I understand why you made a copy of the enum DAO.DataTypeEnum ... so that you can see how to use such an enum. From a clean code perspective, I would avoid this, as it is just one more source of errors and, strictly speaking, does not add any value compared to the direct use of DataTypeEnum...

I was too curious about how the technical implementation of the import could work ... => The package import feature is now up and running. :) Note: Packages can be nested, which makes it easier to organize and manage detailed components in their respective repositories. A test package...

Note: In earlier Access versions (I assume with VBA 6) you could export the class, set the attributes VB_Creatable = True and VB_Exposed = True and then import it again. Then the class could also be created from the Lib file with New. I just tested this with VBA7 (64 bit) and it no longer worked.

Test: Msgbox Dir("C:\Windo*", vbDirectory)

Probably here: https://www.access-programmers.co.uk/forums/account/ignored

Note: I am also expanding my existing add-in with some features that I can also use without a "catalog". New: Package tag: only the content of the file is read, but it is not imported Use tag extended: you can now directly enter a GitHub reference to a code module. Examples: VBA-JSON package...

Find and import ... the functionality of npm or nuget for Access/VBA.

Comfort quickly becomes the norm. ;) Who knows this procedure: Initial situation: A sample file (accdb) contains the required code modules. Now you go to your application, click on Import external data, select the sample file, go to Modules, click on the required modules and import them. Then...

I know doxygen and Natural Docs.