Can't you just do a select statement to check if the record already exists?
Steeve...
-Message d'origine-
De : RHODPR [mailto:[EMAIL PROTECTED]
Envoyé : 27 octobre 2004 05:54
À : [EMAIL PROTECTED]
Objet : [development-axapta] error catching when inserting in SQLServer
Hi all,
Yes I can, I know that is an option. But is there any way to catch
such an exception? Maybe there will be other exceptions that are
thrown by SQL Server, I just want to know if it's possible to catch
them...
--- In [EMAIL PROTECTED], "Steeve Gilbert"
<[EMAIL PROTECTED]> wrote:
>
> Can
TECTED]
Objet : Re: RE : [development-axapta] error catching when inserting in SQLServer
Yes I can, I know that is an option. But is there any way to catch
such an exception? Maybe there will be other exceptions that are
thrown by SQL Server, I just want to know if it's possible to catc
Hi Steeve,
What you are doing is correct. I don't have an EmployeeTable so I have
used the CustTable. Create a job and try this.
Here is my code:
CustTable custTable;
;
try {
custTable.initValue();
custTable.AccountNum = "0";
custTable.Name = "Tom Hoeber
Also remember that you have to put the try catch outside your outermost
ttsbegin/commit.
A throw will always go outside of that, as far as I know.
Eks:
CustTable custTable;
;
will NOT work:
ttsbegin;
try {
custTable.initValue();
custTable.AccountNum
e class Statement and ODBCConnection to execute the query.
Steeve...
-Message d'origine-
De : RHODPR [mailto:[EMAIL PROTECTED]
Envoyé : 27 octobre 2004 10:28
À : [EMAIL PROTECTED]
Objet : Re: RE : [development-axapta] error catching when inserting in SQLServer
Yes I can, I
6 matches
Mail list logo
