Nope! That wasn't it either.....confusing, but not limiting. I can handle not checking for Null in this situation as it can be handled elsewhere.
Nope! That wasn't it either.....confusing, but not limiting. I can handle not checking for Null in this situation as it can be handled elsewhere.
Nope, that didn't do it either....It simply doesn't like me trying to control the object on insert/update. I can change the value check on the right side of the set statement so that's where I'll go with it.
I thought you found the issue? Is it still not working?
How about posting your updated code.
i would also try declaring Dim cProject As clsProject outside the click event and disambiguate your recordset as a DAO.Recordset.
this line doesnt look right to me
Code:Public Property Get Recordset() As Recordset Set Recordset = prsRecordset End PropertyIsn't the nz on the wrong side of this?Code:Nz(.Fields("ClientId").Value) = CLng(Me.ClientId)
If this helped, please click the star * at the bottom left and add to my reputation- Thanks
Sorry for the late reply....I worked late into the night and took advantage of some long needed sleep!
Yes, you are correct....that, I believe, was the issue. I actually changed the null checks (complete with replacement value) on the right side of the set statement. I also updated all my classes to set the Recordsets to DAO to eliminate ambiguity.
Everything is now running stable and as expected.
I got lazy when I created the classes and was going through the motions (that's what got me). Between not being explicit and not watching how I built the class, I made a couple mistakes. When I get a little time I'll upload a stripped down version of how the classes are working in the app.
This can be considered closed as you hit the nail on the head.
Null check on wrong side of the value assignment and not explicitly declaring the recordset.
Micron and I were happy to help.
Good luck with your project.
If this helped, please click the star * at the bottom left and add to my reputation- Thanks