Upgraded to Access 2003 Problems

[dontay]

Hi All,
The company I work for is upgrading from Access 2000 to Access 2003. They are using Windows 2000.
Now Access 2000 applications are not working on Access 2003. The forms command buttons that use to run reports are getting error messages about the queries that the reports run off of, and I can't open the reports in design view.
I tried to use the convert database tool to convert it to 2003 but that did not fix it.
Is there something different with the code between Access 2000 and Access 2003?
Thanks for any ideas.
Don

 

[easyit]

hi,

Could it be that the access apps are compiled into mde's? Than you could have references that are broken.

other than that I have had no trouble between 2003 and 2000 (I develop on 2003 & 2000 but all apps are being used on 2000).

Try checking the references...

EasyIT

 

[THWatson]

This is a fascinating story. Some people, such as easyit, have no problems whatsoever in moving to Access 2003. Other people have nothing but problems. I fall into this latter category.

On two different occasions, I have installed 2003, only to revert to 2000.

If you want interesting reading, have a look at thread181-1157765.

Tom

 

[easyit]

Ah,

I forgot about a ugly period. I once had 2003 installed as an upgrade to 2000 - and that was sh*tty. after deinstalling 2000 and reinstalling 2003 I had no problems anymore.

Sorry, it was a while back.....

 

[dontay]

Well, it's not a mde file. The I.T. guy at work thanks that the code is different for 2003 but after checking Tek-Tips, I don't see that mentioned at all. It's starting to look like a bad install?
Thanks everyone for your help.

Don

 

[PHV]

getting error messages
Which messages ?
Did the code compile properly in 2003 ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[dontay]

I'm not at work right now so can't give you the exact error. But, the application runs about 4 reports and none of the preview report command buttons do anything. And the print report command buttons generate query error messages that I can't quote right now.
The computer that was upgraded is my office manager's. The application is on a network and it still works fine on my access 2000. In addition there are other access programs that are behaving in similar ways for her sense she upgraded to access 2003. Both the 2000 access database that I use and the new converted 2003 database are not working for her.
I was hoping that it was a common problem. But it looks like there is something unique to her situation.

 

[Tigerlili3]

Just an idea...

You may be having a problem with VBA references. On the Access 2003 machine, select Tools|References... from the menu in the VBA editor. You may notice that some of these are marked MISSING. Access 2003 uses Microsoft Access 11 Object Library where Access 2000 is using a different version of this file. When Office 2003 was installed, it is likely that your IT folks uninstalled Office 2000 which would have included different VBA reference files than Office 2003. Check the list of references on a machine with Access 2000 where the application is working and make note of them. Go to the Access 2003 machine and verify that all of the equivalent references are selected.

 

[dontay]

I added the references from the 2000 machine. But that did not fix it.
I did find out some interesting information though. The aplications work fine if the default printer is the (Microsoft Office Document Image Writer)that comes with Access 2003, But if I make the network printer the default printer, I can't even preview a report. That's weird but true.
Is there a way to set preferences that will allow the application to print to a network printer?
Thanks everybody
Don

 

[easyit]

...have you installed the latest update for office2003?

Also, reports are tied to printers; goto page setup to set the printer.

We;ve had similar problems on o2k, and it was solved with a patch. I will see what that was...

 

[Dor100]

This thread may be able to change your life: thread705-1192709.

 

[easyit]

other options that I can think of:

decompile your db's
did you convert your db's or not?

 

[dontay]

In both cases of converting it and not converting it, it does not print when the network printer is set to the default printer. And I can't even open a report in design view.
I told the IT department about it and now I get to see what they figure out. I will post the solution if they find one.

Don

 

[x112358]

I just came across this same issue on a fresh install of Office 2k3 on a new machine. Everything worked perfectly until the user tried to run an Access report, and suddenly we get nothing. Trying to enter code view to see the VBA also caused Access to hang -unless I clicked an object first-! Strange stuff. Anyway thanks to easyit for calling the printer bug. I switched over to "MS Office Document Image Writer" and everything is suddenly ok. Oh yeah and thanks, Microsoft, for so viciously entangling what appears to be unrelated.

 

[dontay]

Our IT department has not solved the problem yet. I can work around it by switching over to the "MS Office Document Image Writer" and it works. But if I want to use the default printer that is on the network, it hangs up. Has anyone found the fix so I can use the network printer as the default printer?

Some kind of printer bug!!!

This is the best site in the world.

Don

 

[PHV]

Have you applied the Office2003 Service Pack 2 ?
Have you tried to change the printer driver ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[dontay]

I just work in the office, It's up to the IT department to perform updates and install drivers. Even though it's got them stumped, they would not apppreciate my unsolicited advice. Are all IT departments like that?
At least I got it to where it works.

Thanks everyone.