Solved

Error Exporting From Access Application VBE6EXT.OLB

Posted on 2013-06-11
1
773 Views
Last Modified: 2013-06-12
In an Access 2003 app I have developed, I created a right click (shortcut menu) that I include on all reports.  The options on this menu are all pulled from MS menu's, there is no special coding.  The options are Print',  'Export' and 'Mail Recipient as an attachment'.

This app is used at over 20 installations and these functions have always worked as they should.

I got a call today from a user running Windows XP, that is getting an error when he tries to export.  The entire message is in the attached file but it generally is about a broken reference to 'VBE6EXT.OLB'.  I aksed what changes he made to his computer recently.  Turns out someone tried installing some other kind of software on his computer last week, the problem has since come up.

It seems very clear that the other software caused this issue but he is a long time, very good customer so I am trying to help him out.

Our software is installed using Sagekey and I completely uninstalled it and re-installed it.  Same error.

I did some reading which said that maybe VBE6EXT.OLB had gotten corrupted.  I copied the good file from my machine to his machine and got a new message when I tried to export a report.  Something about the proper components were not available to export Excel, RTF, etc...

When I removed my copy of VBE6EXT.OLB and re-used his, the same old message in the attachment came up.

Any ideas on what I can do to resolve this for him?  I am not a registry editing type of guy but something tells me that might be necessary in this case.

Thanks in advance for any help.VBE6EXT.OLB-Issue.docIn an Access 2003 app I have developed, I created a right click (shortcut menu) that I include on all reports.  The options on this menu are all pulled from MS menu's, there is no special coding.  The options are Print',  'Export' and 'Mail Recipient as an attachment'.

This app is used at over 20 installations and these functions have always worked as they should.

I got a call today from a user running Windows XP, that is getting an error when he tries to export.  The entire message is in the attached file but it generally is about a broken reference to 'VBE6EXT.OLB'.  I aksed what changes he made to his computer recently.  Turns out someone tried installing some other kind of software on his computer last week, the problem has since come up.

It seems very clear that the other software caused this issue but he is a long time, very good customer so I am trying to help him out.

Our software is installed using Sagekey and I completely uninstalled it and re-installed it.  Same error.

I did some reading which said that maybe VBE6EXT.OLB had gotten corrupted.  I copied the good file from my machine to his machine and got a new message when I tried to export a report.  Something about the proper components were not available to export Excel, RTF, etc...

When I removed my copy of VBE6EXT.OLB and re-used his, the same old message in the attachment came up.

Any ideas on what I can do to resolve this for him?  I am not a registry editing type of guy but something tells me that might be necessary in this case.

Thanks in advance for any help.
0
Comment
Question by:mlcktmguy
1 Comment
 
LVL 84

Accepted Solution

by:
Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 250 total points
Comment Utility
You might try a repair install of Office/Access. That may fix your references (and the dependency chains for all the references).

However ...

VB6EXT.OLB deals with Visual Basic Extensibility. It's not common to have this reference checked, so are you sure that you need it?

You can check it like this:

1) From the VBA Editor click Debug - Compile. Fix any errors, and continue doing this until the menuitem is disabled.
2) Compact the database
3) From the VBA Editor click Tools - References. Uncheck the reference for the VBA Extensibility library.
4) Now compile again.

If the Compile in Step #4 works, then you don't need the reference. If it does NOT work, then please post back here with the code the compiler finds - I'd be interested in what  production app needs from that library (and there may be other ways to fix this).
0

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Join & Write a Comment

It is only natural that we all want our PCs to be in good working order, improved system performance, so that is exactly how programs are advertised to entice. They say things like:            •      PC crashes? Get registry cleaner to repair it!    …
Overview: This article:       (a) explains one principle method to cross-reference invoice items in Quickbooks®       (b) explores the reasons one might need to cross-reference invoice items       (c) provides a sample process for creating a M…
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
Learn how to number pages in an Access report over each group. Activate two pass printing by referencing the pages property: Add code to the Page Footers OnFormat event to capture the pages as there occur for each group. Use the pages property to …

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now