Wizzard errors in Access 95 on NT 4.0

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.
 

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.

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.

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.