[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 674
  • Last Modified:

Error #48 Loading Dll in access

Hi experts,
Im developing a project in access that generates powerpoints based on the information a user selects from an access 2000 database. Everything was going fine until all of a sudden when trying to run the code I recieved the following error.
'  Run-time error '48':    '

'  Error in loading DLL     '
the following line of code is where the problem is pinpointed by the debugger

Set ppApp = CreateObject("PowerPoint.Application")

I have checked the references and Microsoft Powerpoint 9.0 Object library is selected

I have also checked another machine in the office running on windows 2000 to see whether is was a problem with the code but it worked there without any hassles.

I have also tried repairing office from add/remove programs which didn't work and i have fully uninstalled and reinstalled office2000 all to no avail.

I Have noticed the error message refers to a problem loading a DLL when the MSPPT 9.0
( the one used in the above code?) object library is a .obl file. Possibly a generic error message or problems with other DLL's Linked to it?

3 Solutions
On the problem machine, try unselecting the library, saving, closing Access, opening again then reselecting it.
rdun2564Author Commented:
When I unselect it close access and then open it again and then try to re-select it, it has been replaced by MS Powerpoint object library 11. This was previously added to the computer by accident and has since been removed but still shows up now in the references at it's old location on the server. I can always find the proper reference in program files but this example highlights the machines reluctance to use MSPPT9.obl. instead opting for the deceased MSPPT.obl
Make sence?
rdun2564Author Commented:
Despite the library being defunct I have a feeling other libraries are somehow connected to it rather than the 9.0 version. Is it worth checking this? If so how?
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

It may be that the Office uninstall didn't uninstall the object libraries properly.

It seems you have identified the DLL's in question. You could unregister the v11 DLL and reregister the v8 DLL. Though there is a small chance it will fix it, and a large chance that it will wreck your registry!!!

There may be something on the MS knowledge base about uninstalling Office 11 properly.
rdun2564Author Commented:
Office 11 was never installed. Only the MSPPT.OBL from office 11 has been used as a reference in access 2000 on the computer. I think this is where the problem has occurred.
Usually once you browse to the correct file and use it it fixes it.
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
<Office 11 was never installed. Only the MSPPT.OBL from office 11 has been used as a reference in access 2000 on the computer. I think this is where the problem has occurred.>

This is exactly where it occurred (and it's a variant of DLL Hell) ... MSPPT.OBL is NOT redistributable, and incorrectly installing and registering this on a machine with a different version of Office can wreak havoc on the dependancies. You can ___try___ browsing to the correct PowerPoint library and referencing this (as nmcdermaid suggested) but it may not work ... if not, try (a) reinstalling PowerPoint, (b) re-installing Office or (c) COMPLETELY unistalling Office and then re-installing. When I say completely, I mean NOT by using the Add/Remove components ... instead search the MS web site for details of completely unistalling your version of Office.
rdun2564Author Commented:
Thanks for all your solutions. Browsing to the correct library didn't fix the problem nor did reinstalling office or powerpoint.
Nothing to really worry about however as i have found a stitch up for getting around it. I simply changed the name of the powerpoint 9.0 library to that of the powerpoint 11.0 library and copied it into the directory where it is trying to read the file from. It's not orthadox but it's working and thats fine with me.

I'll split the points between both of you. Majority to LSM though as completely uninstalling is the most likely to have any effect as it's the only option i haven't tried.
I'll keep the solution in mind for if the computer is ever taken off the network and the file cannot be found.

Thanks again.
I had the same problem - here's what happened in my case.  I installed Office 2007 in parallel with Office 2003 (all other users are still using Office 2003).  No problem, exept that you can't have multiple versions of OUTLOOK installed - okay, not a big deal - I upgraded Outlook to 2007 and bye bye to Outlook 2003.

I opened up a MS Access 2003 database in MS Access 2003 and made a minor change to a report.  Now, all the other users starting getting the extremely helpful "error in loading dll" message on database open.  Weird.  I then remembered that this database creates an email using code, soooo - on a computer that was having the error, I went into a module, clicked 'Tools->References' and sho' nuff - in the list box was 'MISSING: Microsoft Outlook 12.0 Object Library'.

Looks like Access thought it was being helpful and updated the reference to reflect the version of outlook on my computer.  Didn't tell me, didn't warn me, didn't ask me, just made the change.  Thanks for that extremely useless bit of Artificial Intelligence, Microsoft.

Anyway, no problem, just uncheck the missing one and check the 'Microsoft Outlook 11.0 Object Library', right?  Nope, I get a 'Can't perform requested operation' error message.  Whhaaa?

Thankfully, I made a backup of the database before I changed it and just restored the backup instead of banging my head against a wall any further.  Now, any changes that I do on that database will have to be done using a different computer.  Great.

Moral: MAKE A BACKUP before you make ANY CHANGES! :)

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now