I’m having peculiar behavior results.
I have a form with a Tab Panel Object in it.
The Tab Panel buttons are programmed to do things in conjunction with the panel they open
All of that works fine.
The problems occur when the file is opened. I will get alerts that a couple of databases are not open (before any of the forms open) and then the data from the first record of the form shows up plastered over a different for in a different file (I’ve done this on two different computers).
There is not action in the .Initialize procedure that would call the other abs, but they are called from the “panelcontrol” procedure I use with the buttons to call the panels.
Is the “panel control” procedure being called while the form opens? Or is it because I define the Tab Panel as “” in .Initialize to make sure the Default panel is up? Is that the same as calling the
Either way or another, why some of the form information be plastered all over a different form in a different file?
Additional: It definitely has something to do with the panel buttons going off during .Initialize, I get the same error messages when I press the buttons (I took this file home so the files are not in quite the same place as at work).
The data fields that are plastered across the other file (DataFiles_X in the picture below) are synchronized with the data in CapCamp2019 ie: when I scroll through the records, they change on DataFiles_X. However, images stay in place. When I move CapCamp2019, the fields stay where they are on DataFiles_X instead of following the movement of CapCamp2019