Reports Don't Work on New Computers

[BrokenBiker]

Well...here's the deal. Four computers were replaced in our office and now three of them are having problems with the database. The database is written in Access2003 and all computers (the old ones and the four new ones) are running on WindowsXP Professional w/ Office 2003.

The problems that comes up only involves reports (viewing, email, exporting). When they try to view a report, a message comes up

Cannot find object ".

When they try to email or export a report the function is cancelled due to the error.

I'm going to have the computer admin re-install Access to see if that helps.

I've been searching around trying to find some info on various settings that would cause this, but I'm pretty ignorant in this arena. I checked the references in Access and they are both the same. That's about the extent of my knowledge in thise area.

Any insight would be great.

Thanks for the help.
BB

 

[RuralGuy]

Make sure each computer has a *LOCAL* printer defined. It need not be attached but it *must* be defined. A network printer will not be sufficient to eliminate your problem. Just define *any* printer as local. A text printer will do!

 

[BrokenBiker]

Well...as it turns out...

One of the computer's users who was having this problem told me today, "It fixed itself."

???

I didn't change anything. It never ceases to amaze me that software written by a single company can't talk to its sister-software....Goofy stuff.

Oh, well. Chalk this one up to Murphy's Law.

 

[RuralGuy]

My thoughts are that if you didn't do anything to "fix" the problem then you won't need to do anything for it to break again.

 

[johncallaghan]

Is the database split?
i.e. is the data on a back end?

I have encountered this problem when the back end database is changed on the original machine and the back end on the other computers is not the same?

john

 

[The_Doc_Man]

I'm betting that the problem that fixed itself was fixed when someone running Excel or Word had to print something and had to select a printer to do so. Since printer selection is a REGISTRY function, it "sticks" around. And if it was for WORD, all OFFICE routines share the printer setup because that is really a WINDOWS thing that writes to the registry.

 

[BrokenBiker]

My thoughts are that if you didn't do anything to "fix" the problem then you won't need to do anything for it to break again.

I agree. After one of the users told me that "it was fixed", I went ahead and had all the users print something to make sure their printers were all set up properly.

The database is not split...yet. The original db file was used in another 'company' all together. That copy has relatively few users. This one (at my current location) has several users. I'm going to set up a FE/BE version here to avoid the auto-backup problems when Access closes while others are still using the file, but I'm having a 'delete' problem. If I can't figure it out, I'll start a new thread.

Thanks for the inputs!

 

[RuralGuy]

It sounds like you have the problem under control. Good luck with the rest of the project and thanks for posting back with a follow up.