Search results

It does. I was referring to form and report properties, particularly Recordsource and (Control)Rowsource, not the VBA code. Put this SQL into the Recordsource property of a form (deliberately no line breaks): SELECT Column1, Column2, Column3, Column4, Column5, Column6, Column7, Column8...

Good idea in theory. In practice it is insufficiently reliable. Long property values, particularly SQL statements, will be broken up into multiple lines. The line breaks may happen in mid-word and thus defeat your search approach.

I believe you mean what Oracle calls Flashback Query. It appears to be very similar to Temporal Tables on Microsoft SQL Server. However, I'm not sure if this the right tool for this job. In the main-form/sub-form context data of one form might need to be restored but not from other form(s). How...

Making the buttons (appear to) float on their own will be difficult. However, you could put the buttons on a small pop-up form that floats over the report. - This shouldn't be very difficult. This solution is even easier than my pop-up form suggestion and unless you have a real reason not to...

It's not. By comparing the rounded values for equality of the first 4 digits, your criteria only shows values where there is no problem. Instead you should check whether there are records where the first 4 digits are different.

Collections are not persistent objects, they are just variables. As every other variable, they exist as "plain text" in your VBA code and at runtime of the code in memory of the Access process.

Double check whether the concatenated paths are all valid. My bet is: conOutDir is missing a backslash at the end.

I'm not entirely sure about VB6, but I think it does. A definite Yes for VB.Net. And it's a compiler option that applies to all files in a project. You don't need to put the Option Explicit statement in any file unless you want a particular behavior for one specific file overriding the global...

If the database application was created in 32bit and you open it in 64bit Access the first time, the whole project needs to be recompiled for 64bit. - Believe it or not.

I guess, because you named the project "InputBox" and thus created a name conflict.

Loose the "Pre".

"Don't make me (the user) think!" This is powerful and valid design principle for UX design. To declare a variable before use, you must think about its name and type in advance. This slows down inexperienced users quite a bit and regarding the type they may not have a clue. Of course...

It's not working on an in memory recordset but fetching the data anew from the source. @Josef P. explained it already in much detail and supplied evidence supporting these explanations. You're just stubbornly reiterating your incorrect assumptions and refuse to either acknowledge the provided...

No sure whether you agree with me or not. Anyways, the behavior is the same with local (ACE/JET) tables and with ODBC linked tables.

It doesn't. That is indeed a problem in such a scenario. However, if it is about security/permissions, I would integrate restricting the records in the underlying query, preferably on a database server.

And what do you feel is the problem with that?

You are not using the proper delimiters for a date: #

The order in the list of references in the dialog also depicts the priority of the references. Moving a library, which might be potentially missing, to the lower end of the list will reduce, but not eliminate, the risk of this causing problems with functions from other libraries.

Which zip? You must download the XstReader.zip from the releases section, not a zip of the source code.

Strictly speaking the documentation is correct and precise. If you actually deal with an container control, its child controls will be on the container control, not in it. - Microsoft is using this terminology consistently. I agree that the wording in the documentation has some potential to...