Search results

You can write code like below (and more for each container) to get Create and Modify dates, but these are not super reliable. They are sometimes updated even when you think you didn't change anything. Dim ao As AccessObject For Each ao In CurrentProject.AllForms Debug.Print ao.Name...

Thanks for clarifying. Since you attached text files, I wasn't sure if these were sent to you by some other entity. You could have attached a zipped copy of your database, stripped to the bare essentials. I'm thinking your crosstab is a good attempt to get the data for HTS2 - 7, and now you're...

I have a few questions. Please answer all of them. There are good reasons for each of these. 1. Where does Special Duty.txt come from? Do you have any control over its format? 2. Special Duty Crosstab.txt: seems to be the results of a crosstab query over Special Duty data. How was that created...

As I wrote in #5, as long as you are storing the date value as a Date/Time field in the database, you are good. How you format it to display to the user does not matter to the date math and queries. If you are storing your date values in Short Text fields, that is really bad and should be fixed...

Another very important point: there is an important difference between the VALUE of a date, and the way it is DISPLAYED. Under the hood every date is an 8-byte floating point value. We can display it in many ways, such as the several ways mentioned above, and many others. Example (in the...

> "#" & Format([CheckIn], "dd/mm/yyyy") & "#" No, that is no good, because that would result in a date like 31/12/2025, which is not a legal date in US format. You have to either use US format mm/dd/yyyy, or ISO: yyyy-mm-dd

Agreed, especially if you digitally sign them. The other justification is that it is a universal file format, likely to be supported decades into the future.

Only if you need it for just half a year. https://www.accessforever.org/post/deprecation-of-ie-browser-control

I ran a quick test. Looked terrible. External browser may be your best bet.

> Why do I need to KNOW if the input is a BigInt/LargeLarge/Large Number data type? I am the OP and I will explain. I am working on an Anonymizer. The user can select a Converter for each column in each table in the database. One of those converters is called RandomNumber. It takes a few...

Add this: rst.FindFirst reeksletter if not rst.NoMatch then Forms!keuzetitel.Bookmark = rst.Bookmark You always want to test the result of functions that can fail.

Can you please upload a zipped copy of your database, stripped to the bare essentials? FindRecord is a method of the DoCmd object, not of the Form object. Your code currently does not compile, I presume (VBA window > Debug > Compile).

Using the Northwind 2 Developer Edition template, in frmOrderList.Form_Open I add: Me.InsideHeight = 6000 And it does just that. Maybe you can compare the properties of this form with yours, to see what the issue may be.

If Forms(stDocName).Visible Then Unlike the AllForms collection, the Forms collection is the set of open forms. Note this only works for parent forms, not subforms.

I'm guessing you are currently exporting a table, including this time field. Change that to a query, and for the time field use the Format function: select Format(myTimeField, "hh:nn") as Time_hhnn, OtherFields from myTable (note the use of "nn" rather than "mm" which is already taken for Month)...

I thought about the similar CDec, which does indeed work at least for some large numbers, but I like the exact solution by MajP even better.

Ha! I thought of doing something like your MagnitudeLE function, because "123" is less than "456", as a string comparison. Thank you very much.

Note that access to HKLM is not allowed in environments where the user is not a local administrator, unless the app is running with elevated permissions (run as Administrator). And in this particular case, the same path under HKCU (which such users would have access to) is not populated.

The Large Number data type is not very well supported in VBA. FWIW, I am using 32-bit Access 365, with support for large numbers checked. Assuming I have a string value and I want to test if it is a valid Large Number, how would I do it? Large numbers pass IsNumeric - good, but the below...

The path is different for different versions of Access, different bitness, and even different installation technologies. Maybe best if upon first launch of your starter app you ask the user to find their shortcut to Access, and paste the value of Target in the Properties window, so you can save...