Search results

Because you are not running the function from the form that has the txtbox text box control. Read the comment I wrote that I see you deleted:

Maybe try this updated version: Public Function ABKey() 'On Error GoTo ErrHandler 'Dim txtbox As Access.Control you don't need this line if the function runs in the form that contains a textbox control NAMED txtbox; you use Me.txtbox to refer to it; if this is in a standard module you need to...

Why not use some hashing functions (https://en.wikibooks.org/wiki/Visual_Basic_for_Applications/String_Hashing_in_VBA)?

Post your code (using the code tags in the forum toolbar) instead of posting screenshots and someone will correct it for you, we don't want to have to type it all from scratch....

See this post: https://stackoverflow.com/questions/23687970/vba-on-error-goto-errhandler Private sub Foo() On Error GoTo ErrHandler 'do stuff ExitSub: ' clean up before exiting Exit Sub ErrHandler: ErrorHandler.messageBox "ThisModuleName","Foo" Resume ExitSub End Sub

Like theDBGuy showed you in post # 23

Apologies, I see now, the OP was referring the the missing "ExitHandler" VBA label....

you don't define it as a label is a type of control; you add it to your form in design view, you give it name using the Properties window then you can refer to it in VBA.

a string (txtbox) does not have a backcolor property....

Try to fully qualify the wsht variable: https://stackoverflow.com/questions/60140965/applying-code-to-active-workbook-from-another-workbook-error-no-such-a-interfac Cheers,

(y)

Because you have a spelling in the query name...you're missing the "y"

You're very welcome, good luck with your project! Cheers,

As suggested use CTrl+G to open the immediate window and inspect the value of the strPath2 variable. What is the format, mine was a guess, maybe you have it "d-m-yyyy", can't really say by looking at 8-8-2022.....

Try to wrap the field in the Format () function: Format([PH_ISAC], "m-d-yyyy") & "\"

My approach is to store the user access rules in a custom system table (prefixed with "usys") in the back-end itself. That way making changes to what users can see and do in the forms is simply adding\editing data instead of adding\editing code...

If the user doesn't need to interact with the data you can simply have a list box on the form with a column for each query field and simply set its row source to the selected query in the click event of the button(s). The advantage of this over using a subform is that if the name of fields...

Here is what I use, I like to check if the file exists and keep the folder and file names separate, but otherwise similar to previous post: Dim sPattern As String, sFolder As String, sFile As String,sSourceFile as String sFolder = "G:\CLASP\CLASP Tools" sPattern = "RG_" &...

I think when you have MS SQL, Oracle, MySQL, PostgreSQL or similar backends the best approach would be to store the front-ends right in the backend itself. You could have a tblFrontEndVersions table with fields storing the version number, description of changes and a zipped version of the...

Glad to hear you got it working! Usually it is better for the lookup tables such as your OrderStatus to have unique StatusID or Code and a description; this setup allows you to refine\change the description without having to run updates on the actual data table(s) to replace the old with the new...