Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
 Posted - 2005-11-21 : 08:22:44
|
| I have a small application that is MS Access linked tables through to a SQL Server 7 via an ODBC connection. Our main application is the same setup and works fine. The small application doesn't work fine. When a user tries to insert a new record they get an error message which I suspect is something at the server end as otherwise everything is fine.My question is this. I was going to try to do a trace to try to narrow down the possible causes but I'm not sure what I should be tracing to determine why this INSERT isn't working. Any suggestions would be appreciated.Many thankssteve-----------Facts are meaningless. You could use facts to prove anything that's even remotely true! |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2005-11-21 : 08:35:59
|
what error message?Go with the flow & have fun! Else fight the flow  |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-11-21 : 13:42:23
|
| I would filter on the Database and that user's login (or machine or whatever)I would then re-try the various INSERT / UPDATE commands (wrapped with BEGIN TRANS ... ROLLBACK) and see what errors I get out of Q.A. (that Access just might not be reporting in full).Sounds like its ADO version, permissions, timeout, or connecting to something-other-than-what-you-think-they-are!Kristen |
|
|
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
Posted - 2005-11-22 : 03:41:42
|
| Thanks guys I've managed to track down the problem. The original error message wasn't really very helpful but I managed to get more informationsteve-----------Facts are meaningless. You could use facts to prove anything that's even remotely true! |
|
|
|
|
|
|
INSERT TRACE