Hall of Fame

1. Geert_Gr...435,695
2. Hypo190,358
3. epasquier119,388
4. ThievingSix114,279
5. MerijnB100,765
6. EddieShip...99,839
7. SteveBay90,270
8. Johnjces76,539
9. rfwoolf72,023
10. ciuly43,806
11. developm...41,920
12. dougaug39,666
13. BdLm36,630
14. JosephGl...33,910
15. 8080_...31,385
16. thiagoblim...31,064
17. senad29,200
18. rllibby28,955
19. aikimark28,882
20. bokist22,565
21. TheRealL...22,394
22. MvanderK...21,400
23. JonasMal...19,980
24. irishbuddha18,800
25. CodedK18,454

1. kretzsch...1,417,314
2. rllibby1,354,947
3. ciuly1,299,984
4. ziolko776,079
5. EddieShip...732,301
6. Geert_Gr...710,012
7. Madshi662,000
8. Slick812645,363
9. geobul628,081
10. mnasman607,055
11. Workshop...558,515
12. TheRealL...544,826
13. inthe514,714
14. MerijnB506,813
15. Ferruccio68442,154
16. mokule431,295
17. mikelittlew...430,856
18. DragonSl...394,371
19. Johnjces344,558
20. Epsylon324,729
21. esoftbg316,932
22. Lee_Nover297,111
23. rwilson293,576
24. developm...284,302
25. Ivanov_G277,736

	[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!

5.4

SQL identity fields do not update after posting an ADO dataset (Delphi 2006 + SQL Server 2003)

Asked by cbaron in Delphi Programming, Delphi Database

Tags: delphi, identity, sql, ado, update

I am using SQL Server 2005 linked to ADO datasets in Delphi 2006.

I have a table [FCTable] which contains a field [FC_FCRef] which is defined as an IDENTITY field in the sql (auto incremented by the server itself).

I have a piece of code which appends a record to FCTable, sets some fields in the record then posts it. This works fine and when I look at the resultant record in SQL Server manager I can see that the identify field FC_FCRef has been set to a value by the server. The problem is that the ADO data set doesn't see the true value of FC_FCRef and believes it still to be Zero as it's the server side that's set it not the code. This means when the next lines of code try to save the FC_FCRef somewhere it's saving the wrong value.

If I close the open the table the values are re-read and are correct but obviously that's highly inefficient when I'm updating hundreds of records. If I set the dataset CursorLocation to clUseServer then it also works correctly but using server side cursors is not recommended as it's (apparently) very inefficient.

Is there any simple way I can get the ADO dataset to get the correct value for the field?

For your reference the Delphi code is;

{ Create a blank claim record }
FCTable.Append;
{ Complete the record fields }
FCTableFC_Date.AsString := DateToStr(Now());
.
.
.
{ Post the claim record }
FCTable.Post;
{ Update the census record with the claim reference }
CPTable.Edit;
CPTableCP_FCRef.AsLargeInt := FCTableFC_FCRef.AsLargeInt;
CPTable.Post;

Using this code the CP_FCRef simply gets set to zero every time even though the actual record in the FCTable is showing a unique number of FC_FCRef :-(

Get your answer NOW

20091111-EE-VQP-89

SQL identity fields do not update after posting an ADO dataset (Delphi 2006 + SQL Server 2003)

Asked by cbaron in Delphi Programming, Delphi Database

Tags: delphi, identity, sql, ado, update

About this solution