I have an access multiple item form that pulls a list of related cases for the user to view and edit. Selecting a specific record, the user can open that case to edit information on a screen showing the entire record.
It has worked smoothly until this morning it didn't. I had it set as an Open Form macro action using the button's onClick. I included a where condition as
As I said, this has worked. This morning it threw an unspecified error. I deleted it and decided to just code the action. I used:
I'm getting a data type mismatch error (3464) when I try to use this. I cannot for the life of me figure out why this won't work. I'm sure there's something minor I'm doing wrong. I've also tried using "Me.caseID.value" and using the upper case (CaseID) as in the macro, but the fields it is pulling start lower case (caseID). Also, both forms are pulling or using data from the same underlying numeric field. How can they be throwing a data type mismatch.
When I rebuild the macro with the original code, it works, but I'd like to be able to do other things that are more accessible in vba. I don't trust the macros that much because they seem more prone to glitching.
thoughts?
It has worked smoothly until this morning it didn't. I had it set as an Open Form macro action using the button's onClick. I included a where condition as
Code:
="[CaseID]=" & [CaseID]
As I said, this has worked. This morning it threw an unspecified error. I deleted it and decided to just code the action. I used:
Code:
Dim stLinkCriteria As String
stLinkCriteria = "[caseID] = '" & Me.caseID & "'"
DoCmd.OpenForm "frmEditAllegationLevel", acNormal, , stLinkCriteria
I'm getting a data type mismatch error (3464) when I try to use this. I cannot for the life of me figure out why this won't work. I'm sure there's something minor I'm doing wrong. I've also tried using "Me.caseID.value" and using the upper case (CaseID) as in the macro, but the fields it is pulling start lower case (caseID). Also, both forms are pulling or using data from the same underlying numeric field. How can they be throwing a data type mismatch.
When I rebuild the macro with the original code, it works, but I'd like to be able to do other things that are more accessible in vba. I don't trust the macros that much because they seem more prone to glitching.
thoughts?