I know there are some TMS users lurking out there on this newsgroup

I have a grid showing one column from a table (_Name) who's primary key is _ID. I don't want to have _ID as a column in the grid. What I do want to do, however, is draw a picture in a cell depending on the contents of a field in the table.

With a standard DB grid its no problem, the grid and table are kept in sync. With the TMS grid (even with PageMode = True) they don't seem to be.

Can anyone help before I throw the TMS stuff in the bin, which since I've spent ages already converting an app seems to be a shame.

Also I don't want to load into the AdvStringGrid or set PageMode = False since it will take 3+ seconds to populate the grid and I lose the ability to set filters on the table.

Roy Lambert

Roy,

Maybe you've tried it or don't want it but I would set the _ID column's
visibility to false. That way you can still relate to the _ID.

Regards, Harry

"Roy Lambert" <roy.lambert@skynet.co.uk> schreef in bericht
news:ADB324CD-531F-4CF1-B779-6D4810B90092@news.elevatesoft.com...
> I know there are some TMS users lurking out there on this newsgroup
>
> I have a grid showing one column from a table (_Name) who's primary key is
_ID. I don't want to have _ID as a column in the grid. What I do want to do,
however, is draw a picture in a cell depending on the contents of a field in
the table.
>
> With a standard DB grid its no problem, the grid and table are kept in
sync. With the TMS grid (even with PageMode = True) they don't seem to be.
>
> Can anyone help before I throw the TMS stuff in the bin, which since I've
spent ages already converting an app seems to be a shame.
>
> Also I don't want to load into the AdvStringGrid or set PageMode = False
since it will take 3+ seconds to populate the grid and I lose the ability to
set filters on the table.
>
> Roy Lambert
>
>

Harry


Its an option I'd prefer to avoid, but one I know is there. I'm begining to think that the TMS components are more trouble than they're worth. A DBgrid that doesn't stay in sync with the table is (insert your own vulgar comment here), and the fact that a number of events use the visible grid/row where others use the "real" grid / row is a nightmare.

Roy Lambert

Roy Lambert <roy.lambert@skynet.co.uk> wrote in
news:39896626-D0A2-4FA6-B99D-480427D2E832@news.elevatesoft.com:

> Its an option I'd prefer to avoid, but one I know is there. I'm
> begining to think that the TMS components are more trouble than
> they're worth.

I have often felt the same..

A DBgrid that doesn't stay in sync with the table is
> (insert your own vulgar comment here),

I chose to separate the UI from the data myself, and only bought the
TAdvStringGrid. But in doing that I know I'm limiting myself to
manageable-sized sets of data - you mentioned 3 seconds to load
everything, so I can understand that you may have other needs.

> and the fact that a number of
> events use the visible grid/row where others use the "real" grid / row
> is a nightmare.

That is a conclusion I also reached, and my solution is to set column
widths/row heights to zero rather than hide them. That way I can ignore
the visible/real problem.

The only time I hide anything is when I let the user print a grid - I
then hide everything with a height/width of zero, print, and unhide
everything again.

The only way I can use this grid is by having all this functionality in
my own inherited base grid, and never starting afresh. Otherwise I get
lost again, trying to remember how I got round this or that un-intuitive
behaviour. But I'm now fairly happy with my tamed version...

--
Chris
(XP-Pro + Delphi 7 Architect + DBISAM 4.25 build 4 + EDB 1.04 build 3)

Chris


I've actually found a solution which involves creating a calculated field in the table, and a stringlist to hold the selections - not to bad since the primary key is a single integer but to have to jump through hoops like this isn't good.

Roy Lambert

Look at the content of the cell, not the datasource.


That got me too

KevanB