Solved

Problem w/ MS Access on Windows XP and higher than Office 97 apps

Posted on 2004-08-12
8
1,029 Views
Last Modified: 2012-06-21
At work we have an Access DB (written in Access 3.0) that is on server and staff input lots of info about clients. It is fairly complex set up and works pretty well. I do not admin it, this one guy wrote it and takes care of it, but all he knows is Access, no more no less.

I have run into trouble with a few queries when it is installed on Windows XP. I works fine if all I install is the frontend part for this DB and Office 97. But if I install Outlook 2K or 2K3 or any office app higher than 97 then it starts messing up.

Doing anything to the DB is out of the question, how do I 'fix' newer versions of Office or Win Xp to make this not be a problem?
0
Comment
Question by:Bob Stone
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
8 Comments
 
LVL 27

Expert Comment

by:jjafferr
ID: 11784516
What errors did you get?

IF you are sending emails with Outlook 2k sp3 or higher, you will get security message, which is from Outlook, not from your mdb.

jaffer
0
 
LVL 36

Expert Comment

by:SidFishes
ID: 11784745
could be a reference related problem...newer machines are likely not setup with DAO (which is A97)

open the app on the new machine, look at any code page, tools/references ...look for MISSING
0
 
LVL 39

Accepted Solution

by:
stevbe earned 500 total points
ID: 11784757
It is worth opening the db and checking references after you have upgraded other office apps ... sometimes other install packages can mess access up and there is nothing you can do on the install to prevent this, blame it on MS. Open access, fix ant references that say Missing, if none say missing the uncheck 1 reference (Microsoft DQO 3.XX Library is a good candidate), close references box, reopen references and recheck what you unchecked. This sounds goofy but it is true I have seen this before when upgrading from 97 to 2000.

Steve
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 39

Expert Comment

by:stevbe
ID: 11784773
oops ... Microsoft DAO 3.XX Library

Steve
0
 
LVL 9

Author Comment

by:Bob Stone
ID: 11784877
They get the error in Access when running a query thing to make a report page. After inputing data and hitting save and exit, instead on getting a page that they can print they get a little box that says "A run time error occurred in module: Form.frmProductionJobSampling. You don't have permission to view this module." with Continue and Reinitialize buttons, the continue does basically nothing and reinitialize shuts down Access.
0
 
LVL 44

Expert Comment

by:GRayL
ID: 11785476
Check user and group permission under tools, security. Select the form and make sure you have open/run permission for your users.
0
 
LVL 9

Author Comment

by:Bob Stone
ID: 11785646
It works for everyone except those with Windows XP and Outlook 2000.
0
 
LVL 8

Expert Comment

by:Eric Flamm
ID: 11785900
You could just install Access 97 on the machines with a higher level of Office, then run this application from Access 97 rather than Access 2000, XP, or 2003. Otherwise, there's probably a reference problem (as described above), where the application is looking for a type library that doesn't exist on the user's machine. With the missing type library, the code won't compile when called and throws the error, but you can't debug because the code is locked (password protected). If you really want to fix it, you could modify the database so all the code is late-binding, rather than early bound. When you late-bind an object, Access gets it from whatever type library is on the PC and doesn't worry about references.

There's an article on late binding at:

<http://www.granite.ab.ca/access/latebinding.htm

-ef
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Overview: This article:       (a) explains one principle method to cross-reference invoice items in Quickbooks®       (b) explores the reasons one might need to cross-reference invoice items       (c) provides a sample process for creating a M…
In Part II of this series, I will discuss how to identify all open instances of Excel and enumerate the workbooks, spreadsheets, and named ranges within each of those instances.
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
In Microsoft Access, when working with VBA, learn some techniques for writing readable and easily maintained code.

735 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question