New "Table Already Opened...." Error

[ScubaBart]

Been working on this app and have posts in a few othr threads but this is a new issue so warrants a new thread I think.

Starting with form F_Main_Overview, I click the Button "Add / Edit Apiary Details".



This form closes and the dedicated Apiary Details window opens. No problems.



Then I click the Button "Return to Main Menu" and I receive the following error.


The macro that I use for this is exactly the same type I use to open and close other forms and this action was working prior to the latest changes to the F_Main_Overview form. (Using two continuous form sub-forms in the details of the main form.)

Clicking on the Hive Details button and closing the window that pops up for that has the same relative sequence but no errors. And doing that after getting the error returns the normal F_Main_Overview form to normal.




I'm missing something but I don't know what. Attached the freshest version of the file as well so others can repeat the error.

[Welshgasman]

Macros are very hard to debug. I am not going to even try, as you have a bunch of them just for closing a form?

[ScubaBart]

Macros are very hard to debug. I am not going to even try, as you have a bunch of them just for closing a form?

I consolidate similar macros into a single macro container and use the sub-macro feature to isolate the actions. Each sub-macro is for a different form. It's simply a method to organize them.

When in the form and with the button selected, it's easy enough to expand to that specific macro action in the 'Events' tab.

Regardless, the macro called on is pretty basic:

[davegri]

Instead of closing the window, just hide it.

[ScubaBart]

Instead of closing the window, just hide it.

That may be something I consider but I have somehow just solved the problem and I'm not even sure how.

I was playing with the 'Wait for Post Processing' and 'Record' Locks' form properties on both the F_Main_Overview form and the F_Log_Apiary_Main form and the error went away. I then tried to figure out which one addressed the issue and now I can't get the error to repeat even when setting the properties back to where they started.

So I'm not exactly sure what I did but the error is gone so I am off to the next problem.

[Welshgasman]

Can't wait. :-)

[ScubaBart]

Can't wait. :-)

Sarcasm ? (Laughing with you)

[Welshgasman]

Well you are way ahead of me in terms of macros, so I have nothing to offer, sorry. :-)