Interactive Button conflicts in InDesign CS3

Question

I am trying to create what's considered a disjointed rollover image gallery from InDesign to PDF (Interactive Elements).
The basis of my file is this:
- 1 main image area, with white fill, button named: BLANK_STATIC
- 1 thumbnail button named : THUMBNAIL
- 1 image (underneath BLANK_STATIC) named: IMAGE_1
The button behaviors are applied to THUMBNAIL
- Mouse Enter: Hide BLANK_STATIC, Show IMAGE_1
- Mouse Exit: Hide IMAGE_1, Show BLANK_STATIC
Export to PDF, preserve Interactive elements... works 'perfectly'
Now i tell myself "okay, i'm ready to proceed in making more thumbnails and this should apply to all other elements"
The basis of my file is this:
- 1 main image area, with white fill, button named: BLANK_STATIC
- 1 thumbnail button named : THUMBNAIL
- 1 image (underneath BLANK_STATIC) named: IMAGE_1
- 1 thumbnail buttoned named: THUMBNAIL_2
- 1 image (in between layers BLANK_STATIC and IMAGE_1) named: IMAGE_2
I check all my behaviors to make sure everything is shown and hidden given it's proper state.... that's not my problem
what's happening is, regardless if i have BLANK_STATIC always turned on, and the very top arranged layer (or a forced separate top layer), IMAGE_2 Layer will appear right on top... if i move the IMAGE_2 Layer to the very bottom... when i create the PDF, it STILL forces IMAGE_2 layer to the top..
the actual functionality will take place once i start to roll over the items, items will hide/reveal themselves given the proper instances, however on initial load of the file, i'm having a layering conflict/issue.
Can someone help?

Answer 1

I've sent a sample file to Dominic that does what he wants.
Here's the explanation I sent with the file:
First, I changed the yellow button back to a normal frame and put it on a layer on the background. It doesn't have to be a button and doesn't have to overlay anything.
Next, I set the two larger fields (which I call Targets) to be Hidden in their Button options. They won't be hidden in the ID file, but they won't be visible on first glance in the PDF.
Next, I set the Act button (which I call a Trigger) to SHOW the corresponding button on Mouse Enter and to HIDE the same button on Mouse Exit.
The Act Trigger doesn't have to show or hide the other field since it has been set for Hidden when the PDF opens.
I then did the other Trigger button to show/hide it's larger target.
That's it!
This creates the effect you want.