Tab Control and Event OLE Referencing Problem

oldes

New member
Local time
Tomorrow, 03:04
Joined
May 28, 2011
Messages
9
Hi,

I developing a project which relies on Tabs heavly on Forms as a standart GUI style.

I realized that controls' evets such as button On_Click events are having problems with referencing to OLE server with following error.


"The expression On Click you entered as the event property setting produced the following error: A problem occoured while Microsoft Office Access was communicating with the OLE server or ActiveX Control"

I was told that it is a known problem with TAB CONTROL and It seems that first Tabs should be created and then objects should be drag and droped (not copied).

I made couple of tries to copy previosly designed controls on newly created tabs but didnt work.

(MS Office 2003, standart Tab Control comes with access )

I also tried on Office 2010 but I had some problem.

My problem and question are:

Is there a fix for TabControl ???

Is there a way to copy and paste controls on the Tab Control with out creating OLE problems ???
 
I have no problem cutting and pasting controls into tabs. Maybe I'm not following what you mean.

I think the error message is more to do with some code you are running. Can you post your code here or even better, post your database.

Chris
 
sometimes your forms get corrupted subtly.

if you cant fix it, try copying all the controls to a new form, and then copy the code. bit of a pain, but it may sort it.

I have seen forms that work, but which you just cannot make changes. any change sort of "locks" the form, so you cannot run or even edit it. Total pain.
 
Hi All,

After 2 days of painfully testing and trying I finally found the problem..

Most of you UK guys never face this problem because you are using EN version of the systems naturally..

The problem comes from the non-EN characters (in this case TR chars mistakenly) used in the database fields stops running OLE server of EN version Access...

As a habit from my days in Australia I am using EN version of the Windows and applications.. (Win 2008 R2 WEB Server, and Office 2003 EN )

Because I used Tabs extensively and during the test I saw that when I deleted extra tabs which had ill-defined control on it, I tought it was a TAB problem..

I probably could have same error even if I didn't use TAB controls...

Sorry for the wrongly accusing TAB for the error but I am glad to solve this problem because otherwise I had to redesign 300 forms somehow... :)

Kind Regards..
 
By the way,

This is a very nice knowledgebase for Access. Thanks for your effort!!!.
 

Users who are viewing this thread

Back
Top Bottom