The expression On Open you entered as the event property setting....a problem occurred while [app name] was communicating with the OLE server or ActiveX control

Question

I was in design mode on a form with an embedded tab control containing 5 pages...each with a subform. I enlarged the tab control. Then I tried enlarging each subform within each page. Somewhere along the line the tab control lost its color and the tabs whited out. It looked like I had screwed something up, so I cancelled. When I went to reopen, I got the above message. I can't put a breakpoint on it because it throws the error before the form opens. I deleted the tab control, and then every single control from the form and still get the message. I'm completely hosed. Is there anything I can do to salvage this form?

Thanx,

Darrell

---

Darrell H Burns

Answer 1

Hi  Darrell

I would try Compact/Repair first and then decompile the db. Open it using the full notation with /decompile switch.

Nadia

Answer 2

Did that already, to no avail.

---

Darrell H Burns

Answer 3

Sometimes, when there are no records to return, Forms will turn white. Are you having this problem in design view or in Form view? I would look at the data source or row source depending how you set it up.

---

Chris Ward

Answer 4

Hi Darrell,

Did you see below KB article by change? Maybe this would help solving the issue:

http://support.microsoft.com/kb/907337

Hope this helps,

---

Daniel van den Berg | Washington, USA | "Anticipate the difficult by managing the easy"

Please vote an answer helpful if they helped. Please mark an answer as an answer when your question is being answered.

Answer 5

Hi Dani.

That article presumes the error is caused by "You run the VBA code on a computer that uses different non-Unicode language settings than the computer on which you created the event handler, the function, or the subroutine." or by using accented characters. Neither is the case in my situation. I designed the form in Access2010 on a Windows7 machine and it worked fine until I tried stretching the embedded subforms.

Thanx,

Darrell

---

Darrell H Burns

Answer 6

Darrell,

I would go the 'import the form into a clean database' route then.

It is possible that there's a DB corruption issue at play here. (and I didn't see that you tried this route yet).

Also, if this route seems problematic, you can go into the "broken" databse and try to use the .SaveAsText method from the immediate command window. You should then be able to .loadFromText into a clean database.

---

Mark Burns, MCAD, MCP
Sr. Microsoft Access Analyst/Developer
Manager LinkedIn.Com community: Professional Microsoft Access Developers Network (PMADN)

Answer 7

Yep, that was the only way out. Thanx.

---

Darrell H Burns