By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,859 Members | 1,341 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,859 IT Pros & Developers. It's quick & easy.

Access 2007 acwzmain acwztool

Expert 100+
P: 254
Hi folks,

I'm relatively new to Access, but I seem to have drawn the short straw, so I have the assignment for my workplace of looking for problems/inconsistencies in migrating applications to Access 2007 from previous versions. We don't have a lot of Access applications, but even a dozen or so can be an interesting challenge. I have loaded a few that were created in Access 2003 into Access 2007 and all of the ones I have tried have come up with missing references to acwzmain.mde and acwztool.mde.

The Access 2003 installations I have looked at have those databases (containing useful stuff) as part of the installation, but the one installation (mine) of Access 2007 that I have examined does not appear to have them. (I have also found missing references to vidtc3.ocx, Mscomct2.ocx and there will probably be others as I proceed.) I did find one other query posted at another site regarding these (acwzmain and acwztool being missing in Access 2007, but no responses.)

Have others of you seen the same thing? The applications seem to work after I remove the references to them. The wizards (at least the ones I have checked) are still there and operating, but the question is just one of transferring the apps to 2007. Is this the expected behavior?

If it isn't, then I suppose it would indicate that I had a problem with installing Office 2007, and it would be worth knowing that. So far, I have not seen enough installations of it to know for sure that I've got it right or wrong.

If the missing references are the norm, then that's fine with me. I will need to warn everybody who plans to move applications from XP boxes to their new Vista boxes with Office 2007 and I can live with this, but I suspect there will be a lot of people who are going to be very confused. It's my job of the moment to try to reduce that confusion, so I'd really appreciate hearing from anyone else who has taken Access applications created under 2003 (or earlier) and tried to run them under Access 2007.

I imagine other people are going to need to know about this, so even without any specific advice, I'm sure that a few responses here would go a long way toward confirming or disconfirming that we should or should not expect to run into those missing references with (nearly) every Access application moved to Vista.

I have found (and to at least some extent found workarounds for) some other issues that seem to be pervasive. At this stage, I still am not positive whether they are actually pervasive or whether any or all of them are mainly artifacts of my own installation, but my guess is that at least some of them will turn out to be "real". I don' t know whether anyone else is going to be interested in the problems/challenges of migrating to Access 2007, but I would be interested in participating in discussions of the topic if anyone cares.

Apr 23 '07 #1
Share this Question
Share on Google+
1 Reply

Expert Mod 10K+
P: 14,534
Hi Paul

When you move applications from an earlier version of Access to a newer version then you can run into the problem of Missing References. It just means that it's needs to be pointed to the newer version of the libary. I don't know what implications Vista will have on this.

Apr 25 '07 #2

Post your reply

Sign in to post your reply or Sign up for a free account.