Search results

SOLVED! So in a last-ditched attempt to see if the issue wasn't one of corruption, I started commenting out all manner of procedures (and entire modules) to see if that would resolve the issue. It did! The culprit turned out to be the Current event in the subform: - The subform Current event...

Sorry for the delay in response. I thought I had already done that once or twice, but for good measure I tried once more. No luck :( The more I think about it, the more uncomfortable I am with letting the corruption just sit there. If at all possible, I'd like to work through this issue...

There are loads of unbound controls on the main form already. Textboxes, comboboxes, option groups, checkboxes... I use them to dynamically build a WHERE clause to filter the subform's displayed results. The issue is more that Access doesn't even "step in" to the Load event; it's not just...

Augh. No luck. I've never done that before, though, so let me tell you what I did to make sure I didn't muck up at any point. (I'm on Access 2007) My db has a front end that I keep on the network drive associated with my work PC. The FE references the BE tables, which are located in a file on...

Nope. The messagebox doesn't appear until I click-in or close :( Not very surprising, given what I was experiencing when I had the breakpoints in place.

NOOOOOOOOO! :eek: :( How can I check to see if this is the case and start towards fixing it? EDIT2 Additional clarity achieved:The OnLoad event for the main form fires on closing only if I have not already clicked into another control. So it's not firing on click-in and on close, but just on...

Form Corrupt? OnLoad event not firing I have a form w/ subform. Both have event procedures tied to their respective OnCurrent events. What I'm trying to do is, when the main form loads, run a Public subprocedure that lives in the module for the main form. I've been able to create click events...

Well that was embarrassing... Yup, that did the trick. I realized that all the textbox AfterUpdate events called the same procedure, so I just cut out the middle man and called that by name instead. I'm having another issue now. It's unrelated, though, and I think I can figure it out. It...

Intriguing. Sorry for the delay. Weekend, etc., etc. Seems promising, but it's spitting out an application-defined or object-defined error...

I'm trying to emulate a behaviour in Access that I see a lot on web forms: you click out of the active control (into blank space, not another control) and the form fields update appropriately. So I want my users to be able to click on the white space on a form I've built and have that trigger...

Thanks :) But I actually don't even need that. Because the only control that doesn't get its TabStop property changed ends up being the control that the form "tabs" to on refresh, it gets that focus back, anyway! HUZZAH!

No luck. Current record did a good job of stopping the tab key from cycling through any records when the 2nd section of code was commented out, but didn't stop btnHome from getting the focus. Current Page did nothing. But good news! I discovered that the problem lay in the fact that the...

Thanks! I was literally JUST looking at that :) So I've made some more progress. But it's got me stumped again: When I put Me.btnHome.TabStop = False at the top of the AfterUpdate event, and Me.btnHome.TabStop = True at the bottom, it seems to do the trick. So that's the concept proven. YAY...

Ok, so I've made some progress here: I can just set the tabstop property to false for all the controls on the form (or, alternatively, disable all the controls), and then set them all back to their original state, I'll be all set :) Problem is, I'm not familiar with how to do that kind of batch...

So I've got a form: - A set of unbound controls filters (using a dynamically-built WHERE statement) a subform in datatable view. - A set of bound controls displays the currently selected subform record; the two reflect one another. - A set of unbound checkboxes at the bottom allows the user to...

Thanks so much! Sorry for the delay; I wanted to see if it would work first. It's going to take a little more work yet, but the solution of keeping the default values in a table looks like it'll do the trick. Just rather more complicated than I would have liked :P

K, got it to work the way I wanted with the following code in the frmEdit module: Private Sub CountRecords() Dim rst As DAO.Recordset Dim endCount As Long Set rst = Me.RecordsetClone If rst.RecordCount > 0 Then rst.MoveLast endCount = rst.AbsolutePosition +...

Thanks! Thought I already mentioned that this did the trick. Looks like I dropped the ball there. Sorry for the delay :)

Solution posted: http://www.access-programmers.co.uk/forums/showthread.php?t=248231

OK! So the issue turned out to be this (for me) My table had a primary key. In any other situation, this would be absolutely essential, but the creator of this db didn't create any relationships, so I was able to remove the PK and turn it into an AutoNumber field with no duplicates allowed. I...