win 8.1 machine and access 2013 on it - PROBLEM

[chemil12009@hotmail.com]

Hello,
I Develop access 2007 application on win 7 machine,
I try to install the app on PC with win 8.1 machine and access 2013 on it.
Each time I open the my opening FORM the " On Load events" cause error msg " A problem occurred while Microsoft Access was communicating with the Ole server or ActiveX Control "

1. I open the DB with access 2013 version.


2. I check the references, there is no missing one!.
3. I compile several times, no error occurs
4. The DB is split, the DB located in the server machine.
A. Is this language issue? Unicode?
B. This error happens only on machine with win 8.1, why?
Thanks in advance
CH

[ItsMe]

Create a copy of your front end file and look for controls that are Unbound OLE controls. I think they are called Unbound Frame. You can create a hidden reference when embedding or linking to stuff via this type of control.

Also, you will want to check the backend for OLE fields in tables. The same thing can happen in a table. Although, I believe the fix may still be in the front end, by deleting and then creating a new bound control.

[chemil12009@hotmail.com]

Thanks a lot,
If I understand what you saying, the problem occur because of the Unbound Frame, in the front end Forms?, just delete them and create new ones instead?
CH

[ItsMe]

just delete them and create new ones instead?

It could be that easy. The OLE may depend on third party files that do not exist on every machine in the world. So different versions of operating systems, versions of applications, etc. can have an impact. Also, there may not be a third party software application installed that opens/interacts with the necessary file type.

Deleting the control on a form may create the necessary connection to the correct version of software or it may point out a problem where the machine does not have the necessary files to interact with the desired file type.

[Missinglinq]

This type of error usually, but not always, associated with opening a Form, is apparently caused by all kinds of things, and, to the best of my knowledge, it is very seldom, if ever, actually connected with communicating with a OLE server or ActiveX Control!

The most common cause, going by what I've seen online for the past ten years, has to do with using a non-English language with Access, and the need to set the language for non-unicode programs to that foreign language. Here's a link explaining this:

You receive an error message when you start Visual Basic for Applications code in an Access database

And always a possible solution, when things suddenly go phooey, for no apparent reason, is to create a new, blank Access file and Import everything into it.

Also, transferring Access files by way of flash memory sticks has a bad habit of corrupting the file, so if this was how the transfer was handled, you might try copying the file again, taking care to wait 15 seconds or so after you think that the file has been copied.

Linq ;0)>