Search results

You could change Command_152_Click to a Public procedure, and then simply call it at the end of Command_153_Click... Public Sub Command152_Click() ..... code for Command Button 152.... End Sub Private Sub Command153_Click() ..... code for command Button 153.... Call...

Hi - came across your 3183 post and I was wondering if you ever figured out how to fix it. Having the same problem on my latest application...

I'm pretty sure there isn't - I mean, I've posted the code and it's not in there, right? Did you find it in the code somewhere and you're simply being coy? And again - am I somehow not being clear? Is there a better way to state that the code operates just fine if I break anywhere and step...

Yes - if I insert a break point anywhere in the code (including the very first line or the very last line) and either step through line by line or just let it run, it works just fine.:banghead:

I've commented out the push/pop commands and I still get the error.

Given the strange circumstances under which the issue appeared initially, and continues to appear, I'll be very surprised if this can be solved by debugging, which is why I didn't include the code to begin with - I really just wanted to put a post out there that might catch someone's attention...

Something else of note - this form worked fine up until recently. There were no changes made to this procedure recently, and this just started happening. Here's a quick description of the procedure - it's used to add a new name to a list of client contacts. If someone type a name that isn't...

Private Sub cboClientContactID_NotInList(NewData As String, Response As Integer) 10 On Error GoTo PROC_ERR 20 PushCallStack "frmInquiries: cboClientContactID_NotInList" ' Adds a new client contact if they don't already exist 30 Dim fName As String, lName As String, ContactID As...

Also, to be clear, the procedure doesn't call any other procedures (other than an error handler in the event of an error), and nowhere in the code do I have any sort of me.close statement...

I've come across some sort of weird bug. I have a combo box that contains a list of values, but users can add their own if they choose. If the value they type in isn't on the list, the Not In List event fires. Once the procedure is done, the form inexplicably closes. Oddly enough, it only...

Marvelous - thanks! Except when i did that, there was no drop down list. :-(

How do I mark this as solved?

Interesting side benefit - a lot of forms that were taking a looooooooong time to open and save are now working much faster. I've gotta try this shift-open thing about as often as I compact and repair, I guess...

You mean Access can, on occasion, act erratically? I'm shocked! Shocked, I tell you... For the record, I'm on 2007 working in Win7 Pro. I solved the issue...sort of. When I noticed I wasn't having any problems with any othe databases, I looked at the "OnOpen" procedure I have in place for...

Some other interesting information - it's only for this one database. When I open a different database (while leaving the bad one open) the error messages work as they should. Is there a "Current Database" setting for this sort of thing?

OK - this is weird, because when I go through the code line by line, it always hits PROC_EXIT, even if the code is thrown off by an error with a SQL statement. For the purposes of brevity, I left out a procedure at the top that adds the formname to an array used by the error handler, and the...

Well, it should work under these conditions, right? (I use Resume Next during development so when I break during an error, I F8 to the line immediately below the offending code.): Private Sub MyProc() 10 On error goto PROC_ERR 100 DoCmd.SetWarnings False 110 'Offending Code which...

That's what I thought, but it does not. I've tried it and the warning is still disabled. And like I said, every procedure I have in code finishes with a docmd.setwarnings true statement just before the exit line. Every procedure passes through that regardless of any errors (due to handling)...

[SOLVED] Save Changes Warning no longer popping up Periodoically, the "Save Changes?" warning that pops when closing a query whose design has changed stops popping up, and the changes are automatically saved. I've tried going into the immediate window to change SetWarnings to True, but that...

Presumably, the end users wouldn't be able to see this username since, due to the app being a runtime version, all the code will be converted to binary, correct?