Solved

Wizzard errors in Access 95 on NT 4.0

Posted on 1998-02-04
5
224 Views
Last Modified: 2012-06-27
I am running Access 95 (Ver 7.0) on NT4.0 workstation. When using either Form or Report wizzard  the wizzard returns the error "application-defined or object-defined error" during on of the steps. This does not happen in Win 95. I have reloaded access from scratch a couple of times to try to fix any Registry problems that might be causing this.
0
Comment
Question by:ist
[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
5 Comments
 
LVL 5

Expert Comment

by:cekman
ID: 1967502
Following is text from a MS KB article - hope it helps:

PSS ID Number: Q139041
Article last modified on 05-07-1997
 
7.0 97
 
WINDOWS
 

======================================================================
---------------------------------------------------------------------
The information in this article applies to:
 
 - Microsoft Access versions 7.0, 97
---------------------------------------------------------------------
 
SYMPTOMS
========
 
Moderate: Requires basic macro, coding, and interoperability skills.
 
If you use the Error() or Error$() functions to get the textual description of an error message, you may receive the following error message:
 
   Application-defined or object-defined error
 
You may receive this error message when you try to get the description of an error trapped in a form's Error event as follows:
 
   Private Sub Form_Error(DataErr As Integer, Response As Integer)
      MsgBox Error(DataErr)
      Response = acDataErrContinue
   End Sub
 
CAUSE
=====
 
The error message being trapped is Microsoft Access specific. When you pass
an error number to the Error() function that is not a Visual Basic for
Applications specific error, Visual Basic for Applications does not call
back into the hosting application to ask it for the error message.
 
RESOLUTION
==========
 
Microsoft Access 7.0 introduced the new AccessError method that you can use
to return the descriptive string associated with a Microsoft Access error
as follows:
 
   Private Sub Form_Error(DataErr As Integer, Response As Integer)
      MsgBox Application.AccessError(DataErr)
      Response = acDataErrContinue
   End Sub
 
NOTE: The AccessError method will return a string associated only with Microsoft Access errors and Visual Basic errors. It will NOT return descriptive strings associated with data access errors.
 

0
 

Expert Comment

by:npbarker
ID: 1967503
This usually happens when the folders that the wizard files are stored in do not have full read/write permissions for the current user.  This can occur if the application is installed by an adminstrator and then the normal user attempts to run the wizards.

The solution is to log in as administrator and amend the access permissions to the folders to full for everyone.

How this solves your problem.
0
 

Author Comment

by:ist
ID: 1967504
I have this problem no matter who I am logged on as. Even if I am logged on as administrator I still have this problem. NOTE: I have the same problem on all my NT machines.
0
 
LVL 5

Expert Comment

by:cekman
ID: 1967505
I recently read an article stating there was a bug with Access 95 wizards and NT. The solution was to not use them on NT (not good I know). It also stated that the problem was solved in Access 97. If you have a copy of 97 you may try converting and testing it on your NT machine just to see if it takes care of the problem.
0
 

Accepted Solution

by:
vj1 earned 100 total points
ID: 1967506
A revision of Office 95 corrects this problem.  The date on the CD is '0396 Disc Assy...'
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

AutoNumbers should increment automatically, without duplicates.  But sometimes something goes wrong, and the next AutoNumber value is a duplicate.  This article shows how to recover from this problem.
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.
In Microsoft Access, learn how to “cascade” or have the displayed data of one combo control depend upon what’s entered in another. Base the dependent combo on a query for its row source: Add a reference to the first combo on the form as criteria i…
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…

690 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