Logging errors in a table with an SQL backend

[lala]

Hi, another (3rd so far) problem when something worked with an Access BE and doesn't with an SQL BE.

i was using Allen Browne's LogError procedure to log all errors to a table so i can review and fix them.
once i switched to an SQL BE - the errors don't get logged. every single error goes to the error handling of his procedure which means that NONE OF THEM can be logged.

my guess is that his procedure was written to work with MS Access errors and all the errors i'm getting after the conversion are coming from the SQL server and his procedure doesn't recognize them.

any ideas on where i can look or anything at all?? i tried googling but as usual, i'm not wording my search right and don't get the right hits

thank you

 

[spikepl]

1. When you ask for help concerning an error, then always state what the actual error message is, not just the error number, show the code and indicate which line errors - that will be the first question, so you can save yourself a useless roundtrip

2. If you google Allen Browne's LogError there is a number of posts on the web concerning sql server

 

[lala]

1. there is no error, that's my problem. it doesn't log ANY errors.

2. thank you, will check now.

 

[lala]

i'm still checking but so far i'm getting the same results i was getting earlier with my own search.
most of the posts that i get deal with the fact that once you switch to the SQL BE - the code throws an error that it "you must use dbSeeChanges".

i'm already past that point, i've fixed that part, i don't get any errors BUT nothing gets logged.

i'm afraid that his code only catches access errors and not sql server errors.

 

[spikepl]

every single error goes to the error handling of his procedure

So there *is* an error - what is it?

 

[lala]

oops, you're right. i got so caught up in the fact that this is an error logging program that i didn't think to look up the error that i'm getting.

but i can't get it to come up now, i fixed everything i noticed and don't remember exactly what made it come up. anyhow, i will google the error the next time it comes up and will post it here if i can't fix it myself.

thank you!!!!

 

[lala]

ok, in case anyone is interested. since then a few errors got logged and i think i understand what's happening.
the errors i was talking about were sql errors like: this record can't be deleted because the FK_blah_blah is ....

like straight up sql errors. and it seems like those don't get logged. if i get another one of those (hopefully i won't) then i will google it and post back.

and thank you, spike))))