Search results

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...

Maybe your app can update a server table at startup time, and again every 5 minutes, to say "I'm here, this is my name, and I am connected.".

ProductIDProduct NameUnit Price 1Chai$18.00 2Syrup$10.00 3Cajun Seasoning$22.00 4Olive Oil$21.35 5Boysenberry Spread$25.00 6Dried Pears$30.00 This works: first paste the query into Excel worksheet, then copy to clipboard and paste here.

KitaYama apparently knows how to do it: https://www.access-programmers.co.uk/forums/threads/this-sql-problem-is-the-max-amount-of-frustration-i-can-handle-right-now.335021/post-1983269

Maybe this can happen if twinBASIC would pursue integration with Access. It's currently not on the 12-month roadmap though.

Peter Cole has an auto-converter.

MzTools has a pretty nice one; fully configurable. Best 100 bucks I ever spent. ' ---------------------------------------------------------------- ' Procedure Name: $P[CODE_ELEMENT_NAME] ' Purpose: $U[Procedure Purpose] ' Procedure Kind: $P[CODE_ELEMENT_KIND_DESCRIPTION] ' Procedure Access...

Are you sure it's an empty string? They are hard to distinguish visually from a Null value. But this always works: Put the cursor in that field. In the Immediate window (Ctrl+G) write: ?Screen.ActiveControl = "" False ?IsNull(Screen.ActiveControl) True To fix the query, you can wrap with the Nz...

You probably meant: in the PROCEDURE that raised the error. That is the scope where it happened.

I responded to "I would think I can encrypt the tables also". I thought that might mean (if Northwind) Customers, Orders, Purchase Orders, and other user-entered data. If encryption is solely to preserve your intellectual property and desire to have people pay for licenses, that is much more...

Re encrypting the data: I am not a lawyer, but keep in mind that holding back user data is a crime in some jurisdictions. Ensuring only paid users are using your app is an issue well beyond the count of Users in SQL Server. You may want to open a separate thread to discuss it further.

If client has full access to the server, you cannot keep them from gaining full access to the database: https://www.sqlshack.com/recover-lost-sa-password/ However, you can encrypt stored procedures, essentially locking up your intellectual property...