Random text box hovers in form view

[5am]

Hello,



I developed my first form in Access 2010 - All of the fields are linked to one table/database. Everything seems to be working fine until I go through a few records in form view when a text box shows up in the middle of my form. It is duplicate in size to a text box above it (a text box is properly placed) and it hovers (i.e., it is transluscent, not embedded in the fiorm), so the rest of the form is not affected. Still, it makes me nervous. When I click outside Access or scroll up/down or close out of Access and reload the box disappears, but after a few more records, it shows up again. Is there someting wrong with the database, or can I overlook this (although it's an annoying sight to overlook in my otherwise nice-looking form).

I would appreciate any insight to help me resolve this or understand what is going on. Please know that I have no experience with code, however.

Sam
PS I tried to attach a png image of a screen clipping from my computer, but the options to click "OK" or "Continue" do not show for me in the pop up window(although they show if I select "URL". I'm using internet explorer 9 on windows 7 64-bit.

[Missinglinq]

Sounds like corruption to me! If you're saying you know which Textbox is performing the spooky stuff, I would try, in this order, checking between each attempt to see if the problem is resolved:

1. Delete the Textbox from the Form then Re-create the Textbox
2. Create a new Form and Copy everything (Controls, Macros, Code) over to it
3. Create an new Database file and import all Objects into it

Linq ;0)>

[5am]

Thank you Linq - Number 1 did not work - too easy I guess.

As for #2, how does one copy everything (Controls, Macros, Code) to a new form?

Also, is there any explanation for why this is happening in the first place so that I'm not doomed to repeat it?

Thanks again,
Sam

Sounds like corruption to me! If you're saying you know which Textbox is performing the spooky stuff, I would try, in this order, checking between each attempt to see if the problem is resolved:

1. Delete the Textbox from the Form then Re-create the Textbox
2. Create a new Form and Copy everything (Controls, Macros, Code) over to it
3. Create
4. an new Database file and import all Objects into it

Linq ;0)>

[5am]

Thank you Linq - Number 1 did not work - too easy I guess.

As for #2, how does one copy everything (Controls, Macros, Code) to a new form?

Also, is there any explanation for why this is happening in the first place so that I'm not doomed to repeat it?

Thanks again,
Sam

Sounds like corruption to me! If you're saying you know which Textbox is performing the spooky stuff, I would try, in this order, checking between each attempt to see if the problem is resolved:

1. Delete the Textbox from the Form then Re-create the Textbox
2. Create a new Form and Copy everything (Controls, Macros, Code) over to it
3. Create
4. an new Database file and import all Objects into it

Linq ;0)>

[Missinglinq]

To the best of my knowledge, you'd have to physically copy and move everything from one Form to the other.

In Form Design View

1. Select/Copy All Controls and Paste into new Form
2. Select/Copy All Code and Paste into new Form's Code Module
3. One-by-one, in the Properties Pane, go into each event that has an Embedded Macro and Copy it, then Paste it into the matching event in the New Form

BTW, #3 is yet another reason to use VBA code rather than Embedded Macros! Steps #1 and #2 would take about thirty seconds apiece, while #3 could take forever!

If I were you, I'd skip over this step and try the new database file/importing everything step next, and only try copying everything into a new Form as a last resort, given the Macros.

Here are some links to articles by Allen Browne on corruption, its prevention and recovery from same:

Allen Browne on Preventing Corruption
http://allenbrowne.com/ser-25.html

Allen Brown on Recovering from Corruption
http://allenbrowne.com/ser-47.html

More Allen Brown: The Recovery Sequence
http://allenbrowne.com/recover.html

Linq ;0)>

[5am]

Thanks again Linq,

I tried to explain in my initial email that I'm not familiar enough with code to mess with it. I can't even figure out how to access the code module in Form design view, but that's another story.

I recreated the database (exporting to excel, then importing from excel) and I re-created the form from scratch (no copying/pasting from previous forms) two times now. The hovering text box problem continues to occur. If I scroll down the form then scroll back up, however, the hovering text box disappears. So it seems to be purely aesthetic, albeit still annoying. I did keep the same design in both of the recreations and keeping everything on one page is better for our purposes. It may simply be that I have too many text boxes/controls on the form (62 bound controls, 7 unbound labels), and Access doesn't like that. Hopefully, it will just leave it's expression of dislike at that, without gravitating toward corruption. I'll check out those links you suggested to better ensure that. Meanwhile, I'll continue to back things up daily just in case.

Thanks again for your insight Linq - It's helpful to have a 'lifeline'. Because I couldn't find anything about this issue on the internet, I wanted to reply with an update in case someone else has to deal with it. I'll re-update if I come across corruption or any other worthy lessons learned...

Sam