Microsoft Access 97

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
(Redirected from MS Access 97)
Jump to: navigation, search

Navigation

Microsoft Access 97 (8.0)

Overview

Microsoft Access 97 (MS Access 97), also known as Microsoft Access 8.0, is a version of Microsoft Access which was available either as a standalone application or as part of the Microsoft Office 97 Professional Edition office suite.

Bugs

  • Scroll Wheel Juggernaut Mode: If you accidentally move the scroll wheel while displaying a data form in single-record mode (i.e. not "continuous forms" mode), Access starts going through the records one by one until it gets to the first or last record (depending on which way you scrolled); this can take quite awhile, depending on the size of the recordset being displayed and the rendering time for each current record. It cannot be interrupted in any way, except by invoking the Windows Task Manager (ctrl-alt-delete) and killing the process for Access. Ctrl-C and Ctrl-Break have no effect.
  • Lookup Lockup: If the query used to look up a value in a table view is too complex (e.g. includes a union), the entire table view (not just the field/column in question) will become "read-only".
  • Report Preview One-Way Street: When previewing a report ("print preview" or "layout preview" mode), the right-click menu inexplicably leaves off "Design View" as one of the options. If you want to go back into design view without saving/closing/reopening the report, you have to remember that there's a "Design View" option in the "View" menu.

Weaknesses

  • Although it is possible to have a function translate source data (stored in a recordset) into a different format and have the resulting value shown automatically on a form field, it is not possible to have a corresponding routine to accept user-entered data and translate it back into data for storage in the table. It is not possible, therefore, for the user to edit data in a form or query if it has been manipulated in certain ways, including fields in queries above a certain level of complexity as well as any data which is the result of a function.
    • The only known way around this is to have a separate data entry field which is not bound (tied directly) to a data column, and have the update performed explicitly in code.
  • Data from some sources (tentatively: queries of a certain complexity or higher, or possibly certain types of JOINs) cause data in continuous forms to be formatted improperly. The user has to manipulate the form in certain ways (scroll to the end, scroll back, hide and reveal the window) in order to restore the display.
  • There are no official tools for recovering data from a corrupted database file (.mdb)
  • There appears to be a limit on the number of tables/queries which can be open simultaneously. This number is never stated outright, but if you try to open too many forms a message pops up saying "can't open any more databases", and some of the fields on the last form opened may be empty or display improperly.

Minor Annoyances

  • Text formatting in stored Query objects is not preserved.
  • There is no way to set the default view for new queries to SQL; you always have to go through several mouse-clicks to get from the default Design View to SQL View when creating a new query.
  • You can't put comments inside query SQL, although you can edit descriptions for all object types (tables, queries, forms, etc.) and there is a display mode which will show the description next to each object.

Possible Bugs

UNION queries seem to return only unique rows; if this behavior is not desired, some kind of unique information needs to be included in the fieldset in order to prevent rows from being merged. (This is a tentative hypothesis based on one example only.) --Woozle 10:21, 23 May 2006 (EDT)

Some types of JOIN queries will refuse to update, claiming that validation rules are being violated -- even though the underlying tables have no validation rules set. When this error happens, Access needs to specify at least one field that is causing a problem, and how the validation rule is being violated. --Woozle 07:09, 10 November 2006 (EST)