Missing References (Access XP)

Topic

New Reply

Don’t know how, but I’ve now got a missing reference being reported
in Ms Visual basic in access xp.

I suspect its something to do with either installing Add-ins, or an
MS update, both of which I did today.

I’ve un-instlled the add-ins, but that hasn’t helped. I’ve also done
a Detect & Repair.

The program is looking for msoutl.olb in the Office11 directory. I do
not have Office 11, but I do have a file of that name in my Office10
directory.

I’ve tried un-selecting the Missing file reference, and selecting the
Outlook 10 Object Library, but its not accepted.

Any suggestions?

Thanks

Reply | Quote

Replies

Try the following:

– Select Tools | References…
– Clear the check box for msoutl.olb
– Click OK
– Select Debug | Compile

What happens?

Reply | Quote

I can’t do the debug.

When I select OK in the References box after unchecking the “Missing” reference, I get a dialog box saying

Can’t perform requested operation

I noticed also that when I did ALT F11 to open the VBA window, I got a missing dll error (no file named)

Colin

Reply | Quote

Try opening the database with the Shift key held down until the Database window appears. Go to the Visual Basic Editor immediately, without opening forms or reports (to avoid loading any code), and try again.

Reply | Quote

Try opening the database with the Shift key held down until the Database window appears. Go to the Visual Basic Editor immediately, without opening forms or reports (to avoid loading any code), and try again.

Reply | Quote

Close the database and Access and then reopen. Do you know how to use decompile on the database? It sounds like that may be necessary. Also, if you don’t have exclusive access to the database, you won’t be able to change the references.

Reply | Quote

Yes I do have exclusive access to the database.

I’ve tried a re-start with SHIFT, and its crashed both times on me when I compile. I’ll have a read now about de-compile and try that.

Colin

Reply | Quote

Keeps crashing after the compile.

Can’t find anything in my books on de-compile. I’ll have a look in the morning. I’m off to bed now.

Thanks anyway

Reply | Quote

I fear that your database has become corrupted. Here is how to decompile:

Select Start | Run…
Type the following, substituting the correct path and name:

“C:Program FilesMicrosoft OfficeOffice10MSACCESS.EXE” /Decompile “C:Documents and SettingsColinMy DocumentsMyDatabase.mdb”

then press Enter. then try to compile again.

If that doesn’t work, try importing all database objects into a blank new database.

Reply | Quote

Thanks Hans

The decompile command worked perfectly, first time.

Thanks again

Reply | Quote

Thanks Hans

The decompile command worked perfectly, first time.

Thanks again

Reply | Quote

I fear that your database has become corrupted. Here is how to decompile:

Select Start | Run…
Type the following, substituting the correct path and name:

“C:Program FilesMicrosoft OfficeOffice10MSACCESS.EXE” /Decompile “C:Documents and SettingsColinMy DocumentsMyDatabase.mdb”

then press Enter. then try to compile again.

If that doesn’t work, try importing all database objects into a blank new database.

Reply | Quote

Hi Colin

Decomplile is part of life with access databases. Charlotte once said, there are gremlins lurking in the code.

I build a ms-dos batch file for each of my databases so I don

Reply | Quote

I noitce that Hans and John give different versions of how to decompile.

Hans has “run access” /decompile “database”
John has “run access”, “database” /decompile

I use the second, but this makes me wonder what’s the right way.

Reply | Quote

Both work.

Reply | Quote

Both work.

Reply | Quote

In general the order of command-line arguments used to start Access does not matter, except where noted. If you search for “Startup command-line options” in Access Help and check the list of options, the only exception appears to be the /cmd option, which “Specifies that what follows on the command line is the value that will be returned by the Command function. This option must be the last option on the command line. ” Note the /decompile option is NOT listed in Help, as it is officially “undocumented”, though you may find it referenced in the MSKB or elsewhere. For example, see ACC97: How to Repair a Damaged Jet 3.5 Database, which states in part:
[indent]

---

If the corruption involves being unable to open the class module of a form or a report, or the design view of a module, you may want to try the /decompile command line switch. It is strongly recommended that you make a back-up copy of the database before attempting this method. The following is a sample command with the /decompile switch, wherein MSAccess.exe is in its default location and the database DB1.mdb is in the C: folder:

C:Program FilesMicrosoft OfficeOfficeMSAccess.exe /decompile C:DB1.mdb

After running this command from the Run box, you are prompted to compile the database after using /decompile.

---

[/indent]
An explanation I once read stated that the /decompile option is undocumented because it was really never intended for use by end-users.

HTH

Reply | Quote

Hi, Mark D — I thought I’d pick on you to ask, although Mark L , Charlotte and a number of others have talked about the /Decompile switch in this forum. I’ve tried it a couple of times, but have never been sure it “worked” — because I get no prompts to compact afterwards. I’ve had no error message that goes away to make me feel better, it’s just that the database crashes and corrupts here and there, and since it’s gone through iterations from 2.0 to XP, I thought it would be a Good Thing to do. If I don’t get prompted to compact, does it mean that it just didn’t /decompile for me?
thx
Pat

Reply | Quote

Normally after you decomplie, you have to manually compact

Reply | Quote

No, you don’t get prompted to compact. It’s your own responsibility to recompile the code, then compact the database.

If the code in a database has been edited a lot, you will usually see that it compacts to a smaller size after having been decompiled, then recompiled. (And to an even smaller size if you don’t recompile. This can be useful if you want to reduce the size, for example for attaching a database to a post here in the Lounge. But when you use the database, Access will compile the code, causing the size to increase again.)

Reply | Quote

Thanks to both of you guys, Hans, and “SupportForJohn!”
It expanded in size after using the decompile switch, and then compact cut that size in half.
Anyway, I feel better now ..
thx
Pat

Reply | Quote

In general the order of command-line arguments used to start Access does not matter, except where noted. If you search for “Startup command-line options” in Access Help and check the list of options, the only exception appears to be the /cmd option, which “Specifies that what follows on the command line is the value that will be returned by the Command function. This option must be the last option on the command line. ” Note the /decompile option is NOT listed in Help, as it is officially “undocumented”, though you may find it referenced in the MSKB or elsewhere. For example, see ACC97: How to Repair a Damaged Jet 3.5 Database, which states in part:
[indent]

---

If the corruption involves being unable to open the class module of a form or a report, or the design view of a module, you may want to try the /decompile command line switch. It is strongly recommended that you make a back-up copy of the database before attempting this method. The following is a sample command with the /decompile switch, wherein MSAccess.exe is in its default location and the database DB1.mdb is in the C: folder:

C:Program FilesMicrosoft OfficeOfficeMSAccess.exe /decompile C:DB1.mdb

After running this command from the Run box, you are prompted to compile the database after using /decompile.

---

[/indent]
An explanation I once read stated that the /decompile option is undocumented because it was really never intended for use by end-users.

HTH

Reply | Quote

I noitce that Hans and John give different versions of how to decompile.

Hans has “run access” /decompile “database”
John has “run access”, “database” /decompile

I use the second, but this makes me wonder what’s the right way.

Reply | Quote

John

Thanks for the comments.

I already have a number of back-up /defrag etc progs running each night using batch files, and I’ve just written one to do with this database exactly as you’ve suggested.

I’ll include my other db’s at the weekend, when I’ve got time.

Thanks to everyone for their time and comments.

Thanks

Reply | Quote

John

Thanks for the comments.

I already have a number of back-up /defrag etc progs running each night using batch files, and I’ve just written one to do with this database exactly as you’ve suggested.

I’ll include my other db’s at the weekend, when I’ve got time.

Thanks to everyone for their time and comments.

Thanks

Reply | Quote

Hi Colin

Decomplile is part of life with access databases. Charlotte once said, there are gremlins lurking in the code.

I build a ms-dos batch file for each of my databases so I don

Reply | Quote

Keeps crashing after the compile.

Can’t find anything in my books on de-compile. I’ll have a look in the morning. I’m off to bed now.

Thanks anyway

Reply | Quote

Yes I do have exclusive access to the database.

I’ve tried a re-start with SHIFT, and its crashed both times on me when I compile. I’ll have a read now about de-compile and try that.

Colin

Reply | Quote

Close the database and Access and then reopen. Do you know how to use decompile on the database? It sounds like that may be necessary. Also, if you don’t have exclusive access to the database, you won’t be able to change the references.

Reply | Quote

I can’t do the debug.

When I select OK in the References box after unchecking the “Missing” reference, I get a dialog box saying

Can’t perform requested operation

I noticed also that when I did ALT F11 to open the VBA window, I got a missing dll error (no file named)

Colin

Reply | Quote

Try the following:

– Select Tools | References…
– Clear the check box for msoutl.olb
– Click OK
– Select Debug | Compile

What happens?

Reply | Quote