Troubleshooting

This topic will cover reported bugs, patches and work-arounds. The Web version may obviously have more information than your local copy.

As of the time of release (Version 4.0, April 2002), the following are the known issues or bugs:

i) The View tab of the Settings windows is intended to display the View currently in use. It does this by highlighting the entry in the Available Views list corresponding to the loaded interface. This feature can operate improperly if the Analysis button is clicked, but the process of the Analysis is interrupted (for example, by clicking Quit on the Analysis window). The View which was in effect (at the time that the Analysis toolbar button was clicked) remains in effect. However, the View highlighted in the Available Views list will correspond to the default View -- that is, the View with the same name as the MDB.

ii) Right-clicking the name of a Query in the Custom Analysis window does not trigger the Field Selection window for that Query. Only tables can have their fields selected individually. To work-around this problem, simply copy the query you intend to use in the interface, and delete the columns you want to exclude. Obviously, this does not affect the data in the underlying table, and it's functionally equivalent to de-selecting the same fields from the original query. Finally, include the new query in your interface. (If the original query appears in the Data Set list, but not the derived query, you may need to alias, that is rename, one of the columns.)

iii) During the analysis process, a message box appears stating: "Parse failure on "Objective is correlated or not found in 1; if <display> is DateQ in 1 then *, with DATE, is found in 1." with OK and Cancel buttons. Clicking OK results in a series of other similar messages. Clicking Cancel halts the analysis in an uncompleted state.

This error usually occurs after a series of analyses have been performed. It can only be corrected by closing and then reopening the database in use. This is a long-standing problem with the ELF engine (accelf.dll) and if we could fix it, believe me, we would.

iv) The values of subordinate attributes (such as the target field of its Action property) are sometimes shown as (?) in the Lexicon Lookup window, for instance place: Verb: ACTION (?) instead of ACTION (OrderID) or ACTION (HomePhone). (For more on the difference between these two definitions, see the Analysis Script topic.) This problem is related to the fact that some attributes are not used or stored by layers past the first translation layer. The Lexicon Lookup window is actually displaying the contents of thecurrent layer, which after a successful translation will be the last (that is, third). To reset the layer to the first, open the Debug Dashboard and click the L0 radio button, then refresh the Lexicon Lookup window. If the radio button is already set to L0, click L1 then L0.

vi) Changing the Usys ELF Analysis macro (as described in the Express Unattended topic) prevents the Access ELF Analysis toolbar button from functioning when the Phrases window has the focus. To reactivate the Analysis toolbar button, click any other window.

vii) When questions are submitted from the Respond button of Worksheet while the Query window is open concurrently, the Close button of the Query window is not relabelled "Cancel." However, it still works to cancel the current translation, rather than closing the query window. To close the Query window in the middle of a translation, click the upper-right Close box.

viii) The Microsoft Access Records menu item can't be reached using Alt-R from the Access ELF Worksheet. This is because the Worksheet uses the Alt-R combination for the Respond button. One workaround is to use Alt-O followed by the right-arrow key. As a SendKeys string, this is "%O{RIGHT}"

ix) Deleting a column from a crosstab worksheet or datasheet does not remove the column. However, crosstab columns can be hidden using methods such as Format/Hide or dragging its back to its front edge. In addition, individual columns can be removed from the graphs of crosstabs by opening the Chart controls on the Worksheet footer and double-clicking the entries to be removed (then re-graphing). See the Chart topic for an extended example.

x) Access ELF cannot fully handle parameter queries unless the types of the parameters are given in the Parameter list associated with the query. This means that you may have trouble with "informally" written queries, where bracketed parameter markers are simply inserted into SQL statements. See the Worksheet's Open button topic for ways of working around this problem.