Delphi Ado data set auto fresh

Looks like a bug in ADO. This makes no sense that the line would appear but not in the right place. Someone did not a good job along the line.

You could try a direct mySQL set of components. At least they will give better perf, and I suppose the management of updates is easier when the component knows exactly how the DB works.

http://www.devart.com/mydac/

If you still have the same problem with those, then this might be a dbgrid problem. You will then have to try with a DBGrid replacement (there are a few, as stringgrid and dbgrid are the worst visual components of delphi in terms of user interface - I wouldn't be to surprise if they have issues related to DB functionalities)

@epasquier,

Before casting aspersions, you might want to check the Help for Delphi and the TADO components. ;-)  I believe that the TADODataset component is performing as designed and as currently set up.  It is not a bug but a failure to identify all of the necessary property settings. ;-)

@SSSIAN,

Again, look at the Sort property of the TADODataset component.  To quote a portion of the Help entry for the TADODataset component's Sort property:

Set Sort to establish or change the list of fields on which the recordset is sorted.

@epasquier
sorry to ask this question, but I cannot see anywhere the Sort property of the TADODataset component
could you direct me to this
I am using delphi 2007
Due to many reasons I cannot user TADOQuery , nor do I wish to use a third party tool

sssian,

I don't have D2007 available to me; however, you should be able to single left click the TADODataset component and then hit the <F1> key to bring up the Help for it.  Look in the Help for the Property link that will let you bring up the list of properties for a TADODataset component.  One of them should be Sort.  

Basically, you set the Sort property much like the ORDER BY clause of a SQL statement, e.g.:

YourTADODataset.Sort := 'CompanyName'

I believe that the default is ASCENDing (as it is with SQL ;-).

Well, it will be difficult for us to reproduce your environment. You will have to try different things and tell us how it behaves.

The sort property is a good possibility and should be quick to test.

If it does not work, then you should try to identify the source of your problem by eliminating other possibilities. If you download the MyDAC trial version it would at least tell us if the problem comes from TADODataSet or the DBGrid. Then when the problem would be identified it would be time to decide if you should keep MyDAC or not, or find a workaround, or try other tests we might provide to help.

I am pretty sure that the problem is simply that the sort property is not set.  I would seriously doubt that there is a "bug" in the TDBGrid component or the TADODataset component.  If the rest of the world is not yelling about it, then it is probably a simple property setting that has not been set. ;-)

Of course, it may still be necessary to do a refresh on the TDBGrid or the TADODataset once the data has been entered (and the Sort property has been set).

TAdoDataset does not have a true sort property

A descendant must implement it like TAdoQuery or TAdoTable

A grid can override this setting with it's own sorting mechanism
A DBGrid uses the sorting from the underlying dataset

A advanced grid like DevExpress has it's own sorting mechanism independant of the dataset sorting

@epasquier,

the query is 'select * from customer_table order by customer_name' so it SHOULD be sorted whatever the sort property

The data is sorted . . . when it is first puled with the query.  However, the TADODataset is a separate entity from the query and behaves according to its own rules.

believe there can't be bugs and everything is normal

I didn't say that I believed that there can't be bugs; however, I have frequently seen developers start slinging mud at products and their providers (not only CodeGear but MS as well) when the problem is that the developers have sometimes come from a different background/language or they simply haven't delved into the properties or methods available and actually read the information about the purpose of the properties/methods.

As for the D5 and D7 Help being screwed up by CodeGear . . . sorry, I just don't buy the statement that they went back and modified the Help for those 2 and those were Borland products. ;-)

Check out the following link.  It provides a reference as to how to set the Sort property of a TADODataset:

http://www.marcocantu.com/code/md5/ADOSORT.htm

>> The data is sorted . . . when it is first puled with the query.  
>>However, the TADODataset is a separate entity from the query and behaves according to its own rules.
Exact. I said : except that some optimizations prevent the sort to occur dynamically
If TADODataSet was perfect, it would work fine in any case. So I guess its own rules are not that perfect otherwise this thread would not exist

>>I have frequently seen developers start slinging mud at products and their providers
>> (not only CodeGear but MS as well)
True, and I'm a strong defender of MS for certain things. Most of the ones where everybody enjoys complaining in fact. But if I don't like a thing, I will tell also, even if all the world love it. Java for example.


>>As for the D5 and D7 Help being screwed up by CodeGear . . .
>>sorry, I just don't buy the statement that they went back and modified the Help for those 2 and those were Borland products. ;-)

Of course not. They screwed up D2007 help. D5 & D7 help files are still perfect. In fact, D7 is my (and a lot of other people) favorite.

>> Check out the following link.  It provides a reference as to how to set the Sort property of a TADODataset
I know of the Sort property usage. It is just ADO that I don't use. I usualy use Oracle direct access components, with which I never had such a mysterious problem as this one. So I guess some people out there knows how to tackle the "unavoidable problems" encountered by the guys who did ADO components - maybe the problem comes from ADO itself, I did say in my first message someone did not his job, I can't point fingers. You will never convince me that its behaviour is perfect.
Which is why I recommend TRYING myDAC just to eliminate possible causes.

ALL
I have increased the points to 350
I will share the points
Can I state that
Even using
I have even  tested with TAdoQuery , again the grid does not refresh , with the inital order statement

Both methods
require somehing  like
AdoQuery .sort::='customer_name ASC'
TADODateset :='customer_name ASC'

Thanks

increased point value

i don't think the sort will solve your problem at all

i think the only way will be to close/open the query
but ... you have the option of resetting your bookmark to that last inserted record
maybe that would be a viable option for you ?

out of curiosity, i'm having a look into a solution

Geert_Gruwez:  
I  appreciate you looking futher into this.
At the moment the sort is crudely working, but I will have use a option of
the option of resetting your bookmark to that last inserted record

i used this sample to reset the pointer after post

procedure TForm1.DatasetRefresh(Dataset: TDataset);
var bm: TBookmark;
begin
  if Dataset.Active and not Dataset.IsEmpty then
  begin
    bm := DataSet.GetBookmark;
    try
      Dataset.DisableControls;
      try
        Dataset.Close;
        Dataset.Open;
        if DataSet.BookmarkValid(bm) then
          Dataset.GotoBookmark(bm);
      finally
        Dataset.EnableControls;
      end;
    finally
      Dataset.FreeBookmark(bm);
    end;
  end;
end;
 
procedure TForm1.FormCreate(Sender: TObject);
begin
  ADOConnection1.Connected := True;
  ADOQuery1.Open;
end;
 
procedure TForm1.ADOQuery1AfterPost(DataSet: TDataSet);
begin
  DatasetRefresh(Dataset);
end;

                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32: