Unable to see triggers' error message on hp or acer computer

[Guest]

When a trigger send a message with RAISERROR I can't see the message on pc
from hp, acer, ... if the pc has been installed with the default
installation's program.

If I format the hard disk and install manually with a MS' cd I can then see
the errors' message.

I have already asked the hotline of HP and MS but both thought that the
problem was coming from the other side !

Any idea ?

Thanks for any help.

 

[Sylvain Lafontaine]

Using Raiserror with ADP has always been tricky; for example, see
http://support.microsoft.com/?kbid=275057 for ADP2002.

After installing from HP or Acer, you should try installing the latest
services packs for all of your softwares (Windows, Office, Access) as well
as the latest MDAC installation:
http://msdn.microsoft.com/data/ref/mdac/downloads/ .

Also, make sure that the severity level is between 11 and 16.

 

[Guest]

I have installed the latest SP of Windows, Office and Acces and the severity
level is between 11 and 16.

For the kb article you provide I think the problem is the severity level of
0, cause I used RAISERROR with Access 2002 for years, and I saw the message.

I know that I had already this problem with Access 2002, and the only
solution that I found (like for Access 2003) was a clean reinstall (by clean
I mean without the HP's cd of Windows).

So thanks for your answer but still looking for help !

 

[Guest]

I have installed the latest SP of Windows, Office and Acces and the severity
level is between 11 and 16.

For the kb article you provide I think the problem is the severity level of
0, cause I used RAISERROR with Access 2002 for years, and I saw the message.

I know that I had already this problem with Access 2002, and the only
solution that I found (like for Access 2003) was a clean reinstall (by clean
I mean without the HP's cd of Windows).

So thanks for your answer but still looking for help !

 

[Sylvain Lafontaine]

Including MDAC 2.8 and JET 4.0 Service Pack 8?

 

[Guest]

Yes, I always try to install the latest MDAC and Jet to see if it corrects
this long time bug/problem.