Search results

Opening the query is not enough, otherwise the expressions will not be calculated. The functions were not called by calling rs.movelast. (Rs.movelast is good for testing the where condition, grouping, etc.) Of course, it also takes time to run through the data records. However, this is not...

I opened a recordset in VBA and evaluated a calculated field of a query. Of course, I had to scroll through the records in VBA using a loop. How else can you measure the time?

I am now testing mid/instr in a VBA function, mid/Instr directly in SQL and Regex in a VBA function with 65000 data records. Each value was read from the column in a loop over the recordset. Result: mid/instr + VBA function: ~1.8 sec mid/instr in SQL: ~3.8 sec .. why? Regex: ~2.7 sec

RexExp: Interesting question: Was your test with a static RegExp instance or with instantiation per function call?

When the form instance is destroyed (reference counter -> 0). This does not have to be after closing if a reference to the form still exists.

I usually open a small pop-up form that I use to initialize the actual application start. Example attached.

Do you also have the problem when you open the form with Docmd.OpenForm (e.g. from another form or via the immeditate window)?

Note: Public Function txtIsValid(TextToValidate) As Boolean<br>< txtIsValid = Not TextToValidate Like "*[!0-9 a-zA-Z]*" Or InStr(TextToValidate, "-") End Function txtIsValid("!-?") => True vs. Public Function txtIsValid(TextToValidate) As Boolean<br>< txtIsValid = Not TextToValidate...

I seem to remember that I had a similar error message in context with conditional formatting. In my case, however, this was independent of whether the form was set as the start form or was called up manually.

It looks like accde creation will now proceed as follows (symbolic): AccessApplication.SysCmd 603, (FullPathOfAccdb), (FileNameOnlyOfAccde) instead of AccessApplication.SysCmd 603, (FullPathOfAccdb), (replace(FullPathOfAccdb, ".accdb", ".accde"))

Is it the language or the programmer using the languages? I myself prefer to program in C# because it is more "powerful". For example, I would sometimes prefer strong typing or a better interface implementation in VBA. However, this is not an argument against VBA when you consider how widely...

Message from JimChristmas:

Download JsonConverter.bas and import with VBE (Menu: File - Import file) Insert reference to Microsoft Scripting Runtime (Call from Immediate window: Application.References.AddFromGuid "{420B2830-E718-11CF-893D-00A0C9054228}", 1, 0) Now test it: Private Sub TestJson() ' Object =...

Perhaps this is what you need: https://github.com/VBA-tools/VBA-JSON You can append data to the collection and dictionary objects and then generate a JSON string from them again.

Implemented with a VB Script file called by MZ-Tools. Script: https://github.com/AccessCodeLib/AccessCodeLib/blob/master/_tools/MZ-Tools/scripts/ExportReimportCodemodule.vbs

Note on: This can be easily done with MZ-Tools, for example.

How do you ensure in your procedures that they run with the right data set?

Maybe you have Access 32 bit and the ODBC driver is for 64 bit.

varchar: HASHBYTES('SHA2_512', 'joseph') => 0x24D6EDB8DBE2BCA... nvarchar: HASHBYTES('SHA2_512', N'joseph') => 0x866D9B1682FB5DB56DDD86... Different input generates different output. ;)

select HASHBYTES('SHA2_512', N'joseph') , convert(varchar(512), HASHBYTES('SHA2_512', N'joseph'), 2)