Archives of the TeradataForum

Message Posted: Wed, 14 Apr 2004 @ 15:37:11 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Good news.

I have finally fixed the problem that prevents some people from opening the Edit History screen in SQL Assistant.

The fix will be in a new efix (SQLA.06.02.00.02) that should be available from the patch server (on NCR@YourService) next week.

The problem is in Microsoft's DAO control. It appears that something gets corrupted (in the registry I think) and that prevents the control from finding a support file it needs.

There was nothing in Microsoft's Knowledge Base for a 3170 error (what you are really getting) but I did find a workaround for a completely different problem that also works for this one.

It works on my PC so hopefully it will work for everyone else.

A future release will display a 'tool tip' window when you hold the mouse over any cell in the 'Error' column. The tool tip will display the full text that you see in the 'Result Message' field of the Edit History screen. (The result of each statement in the query.)

This (and the ability to update a 'Note' by double clicking on it - already available) should dramatically reduce the requirements for ever going to the Edit History screen. (which is a very costly/slow operation.)

Mike Dempsey
Teradata Client Tools

	<Prev	Next>		<<First	<Prev	Next>	Last>>