	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.2

ACCESS (adp) XP/2003 - SQL 2005 Express Backend + .NET (SQL DEAD LOCK)

Asked by BillyDvD in Microsoft ADP, Microsoft Access Database, MS SQL Server

Tags: ACCESS XP, 2003, SQL EXPRESS

I have inherited this app -
Access adp file runs on the network, calling machines run either Access XP or 2003.
Form is bound to a table in sql 2005 express.
I have added a stored procedure to the database to insert a new row in the table.
The error I get from the .net app is as follows...
=====================================================================================
Error in calling assembly Avon Master Pleat Pack, Version=1.0.0.1, Culture=neutral, PublicKeyToken=null.
      Occured in .Net SqlClient Data Provider.
      ________________________________________________________________________
      Transaction (Process ID 70) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

      Description: An unhandled exception occurred during execution.

      The exception was thrown due to the SQL Server returning a warning or error.
      Please review the stack trace for more information about the error and where it originated in the code.

      Exception Details: System.Data.SqlClient.SqlException: Transaction (Process ID 70) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

      Source Error:
       .Net SqlClient Data Provider

      Stack Trace:
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at DAL.MeasurementHeadersHelper.SaveOLDMeasurementHeader(String BarcodeBegin, String BarcodeEnd) in C:\Projects\Custom Filter\Source Code\CustomFilterRespiratorDatabase.DAL\MeasurementHeadersHelper.cs:line 133
       at Avon_Master_Pleat_Pack.Form1.buttonAccept_Click(Object sender, EventArgs e) in C:\Projects\Custom Filter\Source Code\Avon Master Pleat Pack\Avon Master Pleat Pack\Form1.cs:line 273

      Additional SQL Server Information:
      ________________________________________________________________________
       Server Name:      CF-FS1\SQLEXPRESS
       Error Type:      50000
       Error Level:      13
       Error Code:      52
       Procedure Name:      InsertNewMeasurementHeader
       Line Number:      131
=====================================================================================

WHen making the stored procedur call to the database in the .net application, the acces application is not (to my knowledge) connected to the table performing the insert on.

View the Solution FREE for 30 Days

20091118-EE-VQP-93 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. vadimrapp145,500
2. LSMCons...40,950
3. boag200020,400
4. peter57r15,000
5. LPurvis12,000
6. angelIII9,200
7. tbsgadi7,600
8. matthews...7,200
9. rockiroads7,000
10. TextReport6,000
11. jimpen5,300
12. kelvinsparks5,000
12. BrandonG...5,000
14. rrjegan174,250
15. thenelson4,000
15. cactus_d...4,000
15. nmcdermaid4,000
18. johnb67673,500
19. pteranodo...3,000
20. DatabaseMX2,800
21. reb732,600
22. EugeneZ2,500
22. mwvisa12,500
24. TimCottee2,000
24. cquinn2,000
24. ralmada2,000
24. bmatumbura2,000
24. profya2,000
24. chapmandew2,000
24. aneeshatti...2,000
24. jrfaust2,000
24. bigbillydot...2,000
24. bokist2,000
24. lwadwell2,000
24. cwood-...2,000
24. carl_tawn2,000
24. tigin442,000
24. kprad2,000
24. Torrwin2,000
24. dportas2,000
24. GrahamM...2,000
24. Wikkard2,000
24. sb92,000
24. ThrainSon...2,000
24. RPCIT2,000
24. Jubal12342,000
24. JohnSingl...2,000
24. Aaronroach2,000
24. Mestha2,000
24. srikanthre...2,000
24. 8080_...2,000
24. Bobaran982,000
24. vegasIT2,000
24. Notexa2,000
24. necrit2,000

1. vadimrapp1176,950
2. LSMCons...156,475
3. LPurvis101,936
4. peter57r96,986
5. rockiroads51,447
6. boag200044,065
7. capricorn141,518
8. SidFishes37,544
9. jimhorn36,229
10. angelIII33,277
11. stevbe31,815
12. thenelson28,639
13. matthews...27,325
14. nico503826,250
15. DatabaseMX22,750
16. TextReport21,950
17. JDettman21,743
18. kelvinsparks21,700
19. jimpen21,075
20. harfang20,172
21. jefftwilley19,800
22. Arthur_...17,524
23. cactus_d...14,250
24. chapmandew13,748
25. jadedata12,677

ACCESS (adp) XP/2003 - SQL 2005 Express Backend + .NET (SQL DEAD LOCK)

Asked by BillyDvD in Microsoft ADP, Microsoft Access Database, MS SQL Server

Tags: ACCESS XP, 2003, SQL EXPRESS

About this solution