Problem Communicating with OLE Server (Access 2002 SP1)

Topic

New Reply

I have developed some databases using Access 2000 in an NT environment running Windows 2000. I have brought these databases into Access 2002 on Office XP running Windows XP (not an NT environment), However, when running the databases I receive the following error,

A problem occurred while Access was communicating with the OLE Server

Any quick ideas on how to resolve this?

Reply | Quote

Replies

This message commonly occurs when you are using OLE automation, such as when you have a Word document embedded in an Access table or you are manipulating another application from within Access. Without more information, it’s impossible to quess at where the problem lies, but I’d start by checking your references to see if you are trying to reference an application that doesn’t exist on the WinXP machine. Also, did you simply upgrade the database from 2000 to 2002 or did you create a new database and import all the objects?

Reply | Quote

Hi Charlotte,

Thanks for the information. The database uses/controls several other programs such as Microsoft Graphics (which I have had other issues with when using and the system tries to start MS Project) and sending data to MS Word. I checked the references and all appears to be OK. I did not have any Missing References.

As to the database, I both upgraded the database from 2000 to 2002 and created a new database that imported all of the objects but still get the OLE error. (The database still compiles without any errors.)

I will re-check the references as I think this is where the problem is occurring. If not, I can always go back to the old fashioned method and start stripping components out of the database (i.e, the ones using other applications) to determine if this eliminates the problem and points to a solution. Thanks for the help. I will re-post the response when I figure this out.

Reply | Quote

Charlotte,

After re-reading all of the posts, I double checked the forms for Word Documents. Something I forgot is that the the top of each form contains summary information INCLUDING a company logo that was pasted as an object. The logo was provided to me for insertion.

The data properties of this object is as follows:
OLE Class – Microsoft Word 97
Display Type – Content
Update Options – Automatic
OLE Type – Embedded
OLE Type Allowed – Either
Class – Word.Document.8
Enabled – No
Locked – Yes

I would delete and replace the object, however, every time I try to do this in the form design mode I receive the error message and the database crashes. Any easy ways to fix this. Hopefully this will correct the issue as everything else works properly.

Thanks for getting me on the right track. It does not appear that NAV was causing any problems.

Reply | Quote

Has it got anything to do with the installation of Office XP, maybe a Custom install rather than a suggested install?
Just throwing up ideas.
Pat

Reply | Quote

Patt,

You appear to be right on track. Besides other errors I am getting such that access is shutting itself down, I realize that I can’t insert any sub-forms as that functionality wasn’t installed. I then realized that in several databases, only forms with subforms is causing this problem.

I am currently waiting for New Office XP disks to arrive as the originals sent to me with the computer are damaged and can’t be read. I will then do a complete re-install of access, excel, and some other apps and see if this fixes the problem.

Thanks for the suggestion.

Reply | Quote

Pat,

Went through the custom install to ensure everyting in access is installed (as well as other office components), re-checked references, and installed XP Service Pack 2.

I still get the error, however, at least the databases don’t crash anymore.

Interesting enough, Some new databases with similar features developed in XP work fine. I am only having problems with databases designed in Access 2000 (whether converted to 2002 or not).

… Still working on this one.

Reply | Quote

I am having similar problems. DB was developed with windows 2000, office 2000. Moved to Windows XP, Office XP. I get the same OLE server error. Only difference is my database doesn’t have any automation in it. So your problem may be related to something different.

I am also getting errors when trying to import objects from an access 2000 database to an access 2002 database, even tho it is running the db as 2000 (wasn’t converted). It kicks me out of access entirely.

I’d appreciate it if you would post again if you find anything, or send me email. This board is usually my only support line, since no one else here works with Access. I couldn’t find anything on Microsoft’s site.

I’ll try the reinstall. I had done everything else you mentioned.

Thanks. Frances

Reply | Quote

Frances,

I am able to import objects from 2000 to 2002 without error. Don’t know what is happening there with your system. As I stated earlier (in this thread or another), once I installed the latest XP Service Pack, I still get the error, however, the database no longer crashes. I have not had the time to go into the converted databases to determine where the error is occurring. (There is too much code to review and too many areas to strip out and test.)

On a positive note, I am currently working on a DB using Access 2002 and developed on Windows XP Professional with similar features as the other databases and have not had any problems.

I will re-post again if I can figure out what is causing the problem. Based on Charlottes earlier response, I still think the issue is with the references or object models being used that may have changed slightly from 2000 to 2002 (Thus, I will need to evaluate all of the code to see what is causing the error.)

Good Luck. Re-post if you figure out anything.

Reply | Quote

That suggests you might have something like a calendar control version conflict or one of the common controls. There were some changes between the previous versions and Office/Windows XP.

Reply | Quote

(Edited by charlotte on 15-Jan-03 22:18. to add MSKB link)

There is a known conflict with Norton Anti-Virus software that creates this error message in Access 2000. I have had it occur when I have inserted graphics in certain formats.

Here is the reference in the Microsoft Knowledge base: (Q295824)

Peter

Reply | Quote

I don’t use the NAV, so I always forget about that gotcha.

Reply | Quote

,,, So what virus protection are you using…. just curious

Reply | Quote

I’ve used the Command Software antivirus product for years, at least since Symantec bought and suppressed the one I used before that. Unfortunately, Command Software seems to be trying to discourage individual licenses, since their support is all paid and too expensive to subscribe to for an individual, so I may have to find something else. I can guarantee, however, that it won’t be McAfee or Norton.

Reply | Quote

Why ?

Reply | Quote

I don’t think McAfee is adequate and I have a strong bias against Symantec products.

Reply | Quote

I think you may be onto something here. I cant remember if I am using Mcaffe or Norton but will check this evening.

Thanks for the help.

Reply | Quote

Peter,

Thanks for the link. I am using NAV, however, the changes made did not correct the problem. Will try re-installing NAV next.

Reply | Quote

You may want to try the registry hack suggested in the article. I found that worked for me. The other fixes in the options of NAV didn’t seem to do it.

Peter

Reply | Quote