Access 2000 problem opening .mdb

[Socal]

Tried opening an Access 2000 .mdb on Access 2000 and got this error prompt:

Compile error. in query expression ''. -(file info del'd)

I hit OK on that prompt, then a MS VB prompt popped up that said:

Run-time error '2467':
The expression you entered refers to an object that is closed or doesn't exist.

Options for that prompt are either <End> or <Debug> out.

When I get into debug, I do the Tools, References, and:

VB for Applications
MS Access 10.0 Object Library
OLE Automation
MS DAO 3.6 Object Library

are all checked and nothing shows as missing.

Same problem happens with OfficeXP.

Any ideas on getting this file to work? Thanks :)



please move me if i'm in the wrong forum - thx! :-)

[Mntsnow]

Maybe something in this thread about Run time error 2467 will help (http://dbforums.com/arch/105/2002/8/480141)

[BBA]

From Technet: http://support.microsoft.com/default.aspx?scid=kb;en-us;209788


SYMPTOMS
All object collections under the CurrentProject and CurrentData objects contain a Properties collection. However, when you try to refer to the Properties collection of any object in a collection under the CurrentProject or CurrentData object, you may receive the following error message:

Run-time error '2467':

The expression you entered refers to an object that is closed or doesn't exist.
RESOLUTION
Although you cannot use the Properties collection to refer to properties of these objects, you can refer to the properties directly. For example, use: Debug.Print CurrentData.AllTables(1).Name

instead of: Debug.Print CurrentData.AllTables(1).Properties("Name")

STATUS
This behavior is by design.

[Socal]

Thanks, guys.. will check 'em out! :)

[Cowboybooter]

Do you have the Office 2000 SP1 installed, the one that makes it play nicely with VB6?

:)

Bob

[Mntsnow]

She now has sp2 :)

[Cowboybooter]

SP2? I didn't realise there was an SP2!! :eek:

I'll have to go poke about Microsoft Downloads again!

:)

Bob

[Mntsnow]

Hate to burst your bubble CBB but for Office 2000 SP3 is available (http://www.microsoft.com/downloads/details.aspx?FamilyID=5C011C70-47D0-4306-9FA4-8E92D36332FE&displaylang=en) and for OfficeXP SP2 is available (http://www.microsoft.com/downloads/details.aspx?FamilyID=1a8ce553-ab76-4a63-99da-b4ed914c1514&displaylang=en) :D Sounds like you need to get busy downloading :D

[Cowboybooter]

EEK! I haven't paid much attention to office, only winders, guess that must change!

I just looked at the details for SR1a which it said was a prerequisite before SP3, but supported OS's do not include XP?

I am running Office2000 Premium in XP Pro, can I just download SP3?

Thanx for the links BTW Snowman!:)

:)

Bob

[Socal]

HEY! What about my today's Access challenge! *mumblemumble* ;)

Oh.. I've not had the time to try out the suggestions yet.. :o lol but I will and will post back! :bunny:

[Socal]

Eureka! :D I found the fix! w00t! *banana dance*

Referencing the ADO Library (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/pg_introduction_5.asp)

ADO 2.8 Programmer's Guide
In a Visual Basic Application

To import the ADO libraries into a Microsoft Visual Basic application, you must set a reference in the Visual Basic project.

To set a reference to the ADO libraries in a Visual Basic project :


Create a new or open an existing Visual Basic project.

Click the Project menu item and then select References... from the drop-down menu panel.

From Available References, check the box for Microsoft ActiveX Data Objects n.n Library, where n.n stands for the latest version number. The Location field below should identify your choice as $installDir\msado15.dll, where $installDir stands for the path of the directory in which the ADO library has been installed.

If you intend to use ADO MD, repeat step 3 to select Microsoft ActiveX Data Objects (Multi-dimensional) n.n Library . The Location field should identify this choice as $installDir\msadomd.dll.

If you intend to use ADOX, repeat step 3 to select Microsoft ADO Ext. n.n for DDL and Security . The Location field should identify this choice as $installDir\msadox.dll.

Click OK to finish setting the references.