S
s
In my post below I described a problem I have been experiencing since the
client upgraded to Access 2003. I have since found the following article,
which refers to Access 2002 and several posts across the internet where
folks have been finding inconsistent issues that are not tied to a
particular version of Access. Sometimes, the problem occurs in 2002,
sometimes in 2003.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;275057
I wonder if anyone has got a more definitive diagnosis to the problem. ie
are there dll problems or MDAC issues etc.
Any feedback would be truly appreciated.
If I can't get the trigger to raise errors, what is the best work around? I
would like to leave the business logic on the server side if at all
possible, so perhaps a stored procedure would have to be used.
Thanks, Simon
client upgraded to Access 2003. I have since found the following article,
which refers to Access 2002 and several posts across the internet where
folks have been finding inconsistent issues that are not tied to a
particular version of Access. Sometimes, the problem occurs in 2002,
sometimes in 2003.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;275057
I wonder if anyone has got a more definitive diagnosis to the problem. ie
are there dll problems or MDAC issues etc.
Any feedback would be truly appreciated.
If I can't get the trigger to raise errors, what is the best work around? I
would like to leave the business logic on the server side if at all
possible, so perhaps a stored procedure would have to be used.
Thanks, Simon