Archives of the TeradataForum

Message Posted: Mon, 15 Dec 2008 @ 17:20:48 GMT

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

One possibility is that one of the Access dlls is not registered, or was not installed.

Check for the following files in Windows\System32

     MSJet40.dll    4.0.8015.0
     MSJtes40.dll   4.0.8015.0
     MSJInt40.dll   4.0.6508.0
     MSJtEr40.dll   4.0.6508.0
     MSRD3x40.dll   4.0.6508.0
     MSwstr10.dll   4.0.6508.0

Expected version shown in 2nd column. (Should be OK if higher also)

Use a command window to cd to that directory then issue the command

     regsvr32 MSRD3x40.dll

This will register this dll if it is not already registered. (Depending on your rights, Vista may not allow you to do this ... Which might be the root of the problem if you did not have sufficient rights when the application was installed.)

One other file to check for is

     DAO360.dll

This is normally located in:

     c:\Program Files\Comman Files\Microsoft Shared\DAO

but might be somewhere else instead.

This file should also be registered so you can cd to that directory and issue the command

     regsvr32 DAO360.dll

If it still does not work please send me the queryman.mdb file and I'll see if something is wrong with the file itself.

Please also let me know what version of SQL Assistant this is, and whether the problem only occurs on your system. (You could try copying someone else's file and see if it works with that one. [that would only work if it is a corrupted history file])

Mike Dempsey
Teradata Client Tools

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