Recent content by mikenyby

My apologies, I tried to make it as obvious as possible that this advice should not be followed, but I will be more conscientious in the future.

My pleasure. When setting a filter in VBA, what you're writing out in the module is parsed as a string. You only need to enclose the parts of the string that don't change in quotes. You must connect any variables with an ampersand. Additionally, using me.[ObjectName] instead of writing out the...

What is the name of the field that D_Num is bound to? Ensure that the field is in the form's source query. Assuming the name of the form that you are working on is F_ActiveFilesSearch, try Me.Filter = "[Name of field D_Num is bound to] =" & Me.F_Num

Okay so here's what you're going to do. First create a view using this code: [REDACTED] You're good to go! IMPORTANT NOTE: If this is not a school project and you are not asking us to do your homework for you, then absolutely DO NOT do what I described above. If otherwise, go nuts buddy...

@cheekybuddha Frankly, not that great! This is after countless debriefings about how they're prioritizing storing all their data locally....

Thanks for this. I just got out of a meeting with management and now they are saying they want the whole thing on the cloud and a web CRUD app.... >:(

I adjusted this a bit to make it work, but it still may be vulnerable. Here is the new function: Public Function PasswordValid(IntId As Long, strPassword As String) As Integer Dim SP As String SP = "validate_pw " & IntId & ", '" & strPassword & "'" Dim ret As Integer With...

Still the same problem. .Parameters("p1") highlighted with "item not found in this collection".

Is that possible in a pass-through query?

@cheekybuddha your SP works perfectly in SQL Server, thank you! But there are some issues calling it in Access. I'm having a little trouble implementing the Parameters. I've copied the code you have provided, adjusting the data types and variable names used to match my own, but I can't avoid a...

Thanks @cheekybuddha I'll work on it and look forward to your examples.

I do understand how it works, it alters the query that the password validation routine is based off of, here forcing a return of '1'. What I slapped together is a simple stop gap. I frankly don't know what variations would also work. SQL injection is something I've only read about but don't have...

I put this in and it protects against that specific attack, but it won't protect against any other syntax that might work: If strPassword = "'),('1" Then MsgBox "No.", vbOKOnly, "No." Me.txtPassword = "" Me.txtPassword.SetFocus Exit Sub End If

This one worked: '),('1 Do you know a way to protect against this?

The first string brings up the same ODBC error, the second gives us Runtime Error 13, Type Mismatch.