Maximize On Activate

[samjesse]

When I tried to Compact and Repair, it gave the same error as it did On_Activate before.

 

[SOS]

When I tried to Compact and Repair, it gave the same error as it did On_Activate before.

That means you need to fix whatever code is causing the problem first.

That is where you do the COMPILE and see where it takes you and then you fix that.

 

[samjesse]

That means you need to fix whatever code is causing the problem first.

That is where you do the COMPILE and see where it takes you and then you fix that.

Error: Method or Data member not found

Public Function ChoosePeriod()
    
        If IsLoaded("frmTransAndBAS") = True Then

            DoCmd.Close acForm, "frmTransAndBAS", acSaveYes
        End If
        
        DoCmd.Forms!frmChooseDates.Visible = True
        
End Function
and the (.Forms) in the last line in the block is highlighted in blue.

 

[samjesse]

That would be a dll, ocx or olb that isn't registered on that machine.

I am almost sure that this is the case, but do not know how to find out which library is missing.

 

[vbaInet]

Look in the REFERENCES list in your VBA editor (i.e. TOOLS -> REFERENCES) and see if there's any with the word Missing.

 

[samjesse]

Look in the REFERENCES list in your VBA editor (i.e. TOOLS -> REFERENCES) and see if there's any with the word Missing.

I looked and found no "Missing" but looking is not good when there a scrolling list of hundreds of lines in a small window. is there a text search for this list?

 

[samjesse]

I compared the ticked libraries in Windows 2000 and XP and found that 2000 has Microsoft Access 9.0 Object Library where as XP has 12.0 instead of 9.0

 

[vbaInet]

Error: Method or Data member not found

DoCmd.Forms!frmChooseDates.Visible = True

That code is meaningless to the compiler Remove 'DoCmd.'

I compared the ticked libraries in Windows 2000 and XP and found that 2000 has Microsoft Access 9.0 Object Library where as XP has 12.0 instead of 9.0

Got it sorted?

 

[samjesse]

Start > run
regsvr32 "C:\Program Files\Microsoft Office\Office\msacc9.olb"

produced error RegSvr32

C:\Program Files\Microsoft Office\Office\msacc9.olb was loaded, but the DllRegisterServer entry point was not found.

C:\Program Files\Microsoft Office\Office\msacc9.olb does not appear to be a .DLL or .OCX file.

 

[SOS]

It isn't the Windows installation that has to do with the 9 vs. 12. 9 is Office 2000 and 12 is Office 2007, regardless of which Windows installation you have.

 

[samjesse]

So how can I fix this? I googled for no avail. How can I add this library to the list so that I can tick it in.

 

[samjesse]

I have a file on my Hard drive
"C:\Program Files\Microsoft Office\Office\msacc9.olb"

but no item listed in the Reference box for Microsoft Access 9.0 Object Library.

 

[SOS]

So, what versions of Office are installed on what computers? Also, refresh my memory, is this database split and a copy of the frontend on each user's computer?

 

[samjesse]

The database is not split. It is on an XP which has both office 2K and 2007 installed.

 

[SOS]

That would be your problem.

It NEEDS To be split and then if someone with one version opens it (the unsplit and shared frontend) then it will screw things up for everyone else.)

In order for you to set the proper reference for those with 2000 you will have to set it from a computer that ONLY has 2000 on it. And you can't open it with 2007 or it will honk it up again.

 

[samjesse]

It isn't the Windows installation that has to do with the 9 vs. 12. 9 is Office 2000 and 12 is Office 2007, regardless of which Windows installation you have.

but now you indicate that ONLY 2000 needs to run this database.

What if I unInstall office 2007. would that fix it.
i.e.
Is it office or OS problem?

 

[samjesse]

I am happy to run only office 2000 on the XP machine.

 

[SOS]

It is not an OS problem. It is an Office problem.

Access will use replace office references in the file for the latest version that has opened the file. Once that happens then all users with previous versions get reference errors. Running multiple versions of Access can be very dangerous unless you really know what you're doing and have a good reason to do so.

Also, the database really needs to be split and the frontend NOT SHARED as that can be a major source of problems and corruption as well. And as you have it now, it is almost guaranteed that at some point you will suffer some major corruption issues. It is only a matter of time.

 

[SOS]

I am happy to run only office 2000 on the XP machine.

So that means that EVERYONE who runs that database can ONLY use 2000. Nobody can use anything else until you get the split and the separate frontends on their machines.

 

[samjesse]

So that means that EVERYONE who runs that database can ONLY use 2000. Nobody can use anything else until you get the split and the separate frontends on their machines.

Yes. Will do.
*********

Now I went and opened the database in my W2K under office 2000 and all is sweet. the 9.0 Object Library is listed under Tools > references.

I did couple of Compact and Repair to insure all is well. Copied it to the XP Machine which has both offices 2K and 2007 installed. Opened Access 2000 (Not 2007) and opened the database. Went to the Tools > references to find that 9.0 is replaced with 12.0.

I was expecting to find 9.0 since I did not open the database with Access 2007.
How can I fix this.