PLEASE HELP! Incorrect References (maybe) - DB works on one computer but not another?

[Cosmos75]

Not quite sure where to ask this question since I am not sure what exactly is wrong but here goes...

I have a database that I created to keep track of emissions from a paint coating operation.

They enter paint usage daily.

There is a query [qbfMonthlyEmissionsLBS] that pulls together emissions for each day, i.e. that sums up emissions of each constituent for every day that has usage (since one constituent may be found across many coatings and many coatings may be used in one day). The is done for a date range entered by the user via a form (using Between [ReportStartDate] and [ReportEndDate] as a parameter in the query).


Then I have a report [rptQBFMonthlyEmissions] based on that query that is grouped by date and I show the sum for each constituents' emissions. I use the report wizard for this and when you do that it automatically formats the date as a month [(Using =Format$([UsageDay],"mmmm yyyy",0,0)].

So my report show the total individual constituent emissions by month.

This works on my computer (Access 97 , Windows 98) but there is a problem with =Format$([UsageDay],"mmmm yyyy",0,0) on another computer (Access 97, Win NT) . When they try to run the report, it asks the user to enter the parameter Format$??


It's also instead of grouping the emissions by month only shows the total emissions.

The other computer was missing a reference language reference, Microsoft Calendar 8.0 (Mscal.ocx). Well, I added it as a reference. Now the reports groups the emissions by month but there is still a problem with showing the Month and Year for each grouping.

I am attaching a picture of the references used and the sequence. Both computers have the same references checked and in the same sequence.

Does anyone know why this could be happening and what I can do about it?

 

[pdx_man]

Are the versions of mscal the same?

 

[Cosmos75]

Yes, the versions are the same.

 

[pdx_man]

The other computer was missing a reference language reference, Microsoft Calendar 8.0 (Mscal.ocx). Well, I added it as a reference. Now the reports groups the emissions by month but there is still a problem with showing the Month and Year for each grouping.

How did you add the reference? Was the file already on that computer or did you copy the file over. If copied, did you then register it?

 

[Cosmos75]

I copied it over and then clicked browse in the other computer (under references) to reset the link to the file. Is that the same as registering it?

 

[Full_Williams]

Similar Problem

Hi there,

I have a problem with my database when I copy it onto another computer. In the database that's on my computer (Access 2000, Windows2000 Professional) I have some code that adds a list from one box to another: Member's to Inivited Members. When I copy to another computer and try the same function I get:

"Error '3265' Item cannot be found in the collection corresponding to the Requested Name or Ordinal"

I get the error whether it's WindowsXP or Windows2000Pro.

I thought that the refrences would copy with the database.

Any help or suggestions would be appreciated. I'm lost here.

Thank you,
Full Williams

 

[pdx_man]

Unfortunately, it is not that easy. What OS are you using?

Try this. On the computer that is having problems, get to a command prompt and type:

regsvr32 Mscal.ocx

That will register in NT.

 

[Full_Williams]

I guess I should have mentioned that I'm not using a calendar control in my database. Sorry about that.

The error occurs when the code is looking for a parameter off a form. It works fine on my computer which has Windows 2000 Professional, but not on a computer with XP.

I think the problem might have to do with my computer having MS 9.0 Object Library and the others having 10.0 Object Library. The other computer's don't have the 10.0 Library to reference, which blows because I'm thinking I might have to install it. What do you think? This is all new to me so forgive me if I'm totally off.

Thanks,
Full Williams

 

[Cosmos75]

Register on all computers?

pdx_man,

This db on the other computer is actually out on an intranet drive, with more than one person with access to it (db file has a password on it but not set-up for multiple users). Will registering Mscal.ocx on one computer fix it for all computers? Or will that have to be done on all computers that need to use the db file?

 

[pdx_man]

The ActiveX object must be registered on all computers that are running the DB. Depending on other applications that have been previously installed, it may be correctly registered on some computers. But just copying it to the computer will not work. If you have Visual Basic, you can create a distribution package that will install the .ocx. Place the package on the shared box and allow each user to run it to correctly install the package. If it is a very large network, talk to your administrator to have it rolled out the next time a user boots their computer.

 

[Cosmos75]

pdx_man,

So, it's the fact the Calendar Control 8.0 isn't registered that is causing problems with this formula??

=Format$([UsageDay],"mmmm yyyy",0,0)

 

[pdx_man]

Surprisingly, yes that is the root of this error.

 

[Cosmos75]

Guru pdx_man!!

I think I may have tried installing the Microsoft DAO 3.6 Object Library before (was having problems with the switchboard) but that didn't work so instead we choose the Microsoft 2.5/3.5 Compatibility Library which solved that.

I thought I might have been a problem with DAO but now (thanks to pdx_man) I know that it's because the Calendar Control 8.0 isn't registered.

How in the world did you know that the Calendar Control 8.0 needs to be registered in order for Format$([UsageDay],"mmmm yyyy",0,0) to work? Is that just some tid-bit of knowledge you know off the top of your head or is it in some book, Guru Pdx_Man? Is there a place online that I can go search for knowledge like that??

 

[pdx_man]

No, I tripped on that pebble once a couple years ago. Trial and error gave me the answer.