Tim

Other TMS DBAdvGrid users may want to take note.

Using TDBAdvGrid it has a very pretty way of showing wether a row is selected or not. Unfortunately it needs the dataset to be editable to do this (an OnCheckBoxClick event only fires when the grid is editable, even when the column involved is "virtual" ie has no field attached).

The move of ElevateDB to non-editable caned datasets bollixes this up if you've relied on the dataset being editable.

So my question is how do I tell if a query is going to result in a sensitive (ie editable although I'm not going to edit it) dataset?

I don't want to create massive in-memory or temporary tables where I will get a sensitive dataset. I know (or think I know) if I use DISTINCT I'm going to get a non-sensitive dataset (hopefully they'll be fairly small ones) but how do I figure out the others?

Roy Lambert

Roy,

> So my question is how do I tell if a query is going to result in a
sensitive (ie editable although I'm not going to edit it) dataset?

The EDBQuery component has a 'Sensitive' property that indicates whether a
SELECT statement returned a sensitive result set.

regards, Harry

"Roy Lambert" <roy.lambert@skynet.co.uk> schreef in bericht
news:24B5CAF6-4F78-4174-946C-33AC8BC985BC@news.elevatesoft.com...
> Tim
>
> Other TMS DBAdvGrid users may want to take note.
>
> Using TDBAdvGrid it has a very pretty way of showing wether a row is
selected or not. Unfortunately it needs the dataset to be editable to do
this (an OnCheckBoxClick event only fires when the grid is editable, even
when the column involved is "virtual" ie has no field attached).
>
> The move of ElevateDB to non-editable caned datasets bollixes this up if
you've relied on the dataset being editable.
>
> So my question is how do I tell if a query is going to result in a
sensitive (ie editable although I'm not going to edit it) dataset?
>
> I don't want to create massive in-memory or temporary tables where I will
get a sensitive dataset. I know (or think I know) if I use DISTINCT I'm
going to get a non-sensitive dataset (hopefully they'll be fairly small
ones) but how do I figure out the others?
>
> Roy Lambert

Harry


Yeah - I know, but that's after the event What I need is to figure out BEFORE running the query if its going to be editable, if so let it go ahead, if not alter to stuffing the result into an in memory table so it can be editable. Hopefully it'll end up only being small (and fast) result sets that I need to do this for. I would hate to take 25secs to produce a result set to find out its canned and then have to spend 25secs producing the in memory table before someone can use the selection grid.

Roy Lambert

Roy,

>> Yeah - I know, but that's after the event What I need is to figure
out BEFORE running the query if its going to be editable

There's a help topic: "Result Set Cursor Sensitivity" that might help you
out.

Regards, Harry

"Roy Lambert" <roy.lambert@skynet.co.uk> schreef in bericht
news:3470EB08-5D20-484E-BE15-C2E08E22A4D3@news.elevatesoft.com...
> Harry
>
>
> Yeah - I know, but that's after the event What I need is to figure
out BEFORE running the query if its going to be editable, if so let it go
ahead, if not alter to stuffing the result into an in memory table so it can
be editable. Hopefully it'll end up only being small (and fast) result sets
that I need to do this for. I would hate to take 25secs to produce a result
set to find out its canned and then have to spend 25secs producing the in
memory table before someone can use the selection grid.
>
> Roy Lambert
>

Harry


Thanks. That looks like the bumph I was after. All I have to now is understand it

Roy Lambert