Re: handling ado errors
- From: "Marius Kavaliauskas" <markav@xxxxxxxxxxx>
- Date: Thu, 7 Jul 2005 12:44:35 +0300
I have tried to do as you say, but... access sets language back to english
and displays english error.
"Philipp Stiefel" <phil@xxxxxxxxxxxxxxx> wrote in message
news:da3or3.2e0.1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> "Marius Kavaliauskas" <markav@xxxxxxxxxxx> wrote:
>
>> I have ADP (Access 2003) nad I have difficulty handling ADO errors.
>>
>> I have table that has some fields that have to be unique. When enters
>> udplicate data in these fields, he gets an error:
>>
>> Violation of Unique key constraint 'XXX'. Cannot insert duplicate key in
>> object 'YYYY'
>>
>> The main problem is that Form_Error is called and DataErr has the value
>> 2627. How to get the real problem, because I want to thranslate errors to
>> Lithuanian language?
>
> Have you thought about translating the SQL-Server sysmessages table?
> SQL-Server by itself does support localized errormessages and it does
> support the Lithuanian-Langugage (mslangID = 1063). Unfortunately
> AFAIK Microsoft does not supply a localized version of sysmessages
> in Lithuanian.
>
> If you add translated messages to the sysmessages-table of SQL-Server
> and set the appropriate language for the SQL-Server Logins you may
> solve your problem without changing a single line of code in you
> application.
>
> Read the chapter "SQL Server Language Support" in the SQL-Server
> documentation for further information.
>
> Cheers
> Phil
.
- Follow-Ups:
- Re: handling ado errors
- From: Philipp Stiefel
- Re: handling ado errors
- References:
- handling ado errors
- From: Marius Kavaliauskas
- Re: handling ado errors
- From: Philipp Stiefel
- handling ado errors
- Prev by Date: Re: Backup
- Next by Date: Re: handling ado errors
- Previous by thread: Re: handling ado errors
- Next by thread: Re: handling ado errors
- Index(es):
Relevant Pages
|
|