Re: TRIGGER (AFTER INSERT) and Store Procedure ... insert failed !
From: Hugo Kornelis (hugo_at_pe_NO_rFact.in_SPAM_fo)
Date: 09/06/04
- Next message: Tillman Erb: "xp_fileexist to SAMBA-mounted drive"
- Previous message: Erland Sommarskog: "Re: XML IN SQL 2005"
- In reply to: Herve MAILLARD: "Re: TRIGGER (AFTER INSERT) and Store Procedure ... insert failed !"
- Next in thread: Herve MAILLARD: "Re: TRIGGER (AFTER INSERT) and Store Procedure ... insert failed !"
- Reply: Herve MAILLARD: "Re: TRIGGER (AFTER INSERT) and Store Procedure ... insert failed !"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 06 Sep 2004 20:58:44 +0200
On Mon, 6 Sep 2004 16:54:52 +0200, Herve MAILLARD wrote:
>Hi,
>
>Well, I've got the error "ODBC insert failed" (from access front end). If I
>try from Enterprise Manager then I have no error at all.
>I can see that the counter field is not incremented..(stay blank) and when I
>try to refresh the table then my record has been removed.
>
>I agree to post the SP code but it's 2 or 3 pages of T-SQL code.
>I'm trying to remove block by block the code to why wich instruction the
>problem is comming from.
>
>I have no insert into the CR_OF, only some updates.
>
>thanks for your help,
>
>Herve.
Hi Herve,
Try executing the insert that causes problems in Query Analyzer. Both
Enterprise Manager and many front end apps have a tendency to swallow the
real error message and give you something else instead. Or in the case of
EM even no message at all, as you've already experienced.
Also, if you want help finding what's wrong, you'll have to post some code
that can be used to recreate your situation and reproduce the error. To be
precies, you need to post all of the following:
1. Table structure, as DDL (CREATE TABLE statements; irrelevant columns
may be omitted but do include all constraint);
2. Sample data, as INSERT statements (so that we can copy, paste & run
instead of spending half an hour typing);
1/2a. Test your DDL and INSERTS. Create an empty database on your server
and run your code. If you get errors, fix them, test again, then post the
fixed code;
3. Expected output, based on sample data;
4. The code you are currently using;
5. The results you see when you run your code (Do you get an error
message? If so, copy and paste it. Do you get wrong ouput? If so, what do
you get and why is that wrong? etc.)
6. A short and concise description of the business problem you're trying
to solve.
I know that this is a lot of information to post. Most of it is probably
not needed to solve the problem. But you'll never know in advance which
parts will be needed and which parts not; therefor, I do ask you to post
it all.
Some tips and tools to help you in providing the data for a post can be
found here: http://www.aspfaq.com/etiquette.asp?id=5006
Best, Hugo
-- (Remove _NO_ and _SPAM_ to get my e-mail address)
- Next message: Tillman Erb: "xp_fileexist to SAMBA-mounted drive"
- Previous message: Erland Sommarskog: "Re: XML IN SQL 2005"
- In reply to: Herve MAILLARD: "Re: TRIGGER (AFTER INSERT) and Store Procedure ... insert failed !"
- Next in thread: Herve MAILLARD: "Re: TRIGGER (AFTER INSERT) and Store Procedure ... insert failed !"
- Reply: Herve MAILLARD: "Re: TRIGGER (AFTER INSERT) and Store Procedure ... insert failed !"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|