LS

Is refreshing a view the same as refreshing a query in the way that you only
refresh your view of the data locally, so you have to close and reopen to
see actual changes? I thought that -although a view is a 'kind' of query-,
because you see it in the TEDBtable.tablename list the behaviour would be
the same as a table (a refresh there gives you the exact view of the data if
it's changed by another user). It seems not to be so, why?

Regards, Harry.

Harry,

<< Is refreshing a view the same as refreshing a query in the way that you
only refresh your view of the data locally, so you have to close and reopen
tosee actual changes? >>

Not with the latest EDB versions - they allow a true Refresh on queries and
views that perform proper change detection and automatically refresh the
result set as necessary.

<< I thought that -although a view is a 'kind' of query-,because you see it
in the TEDBtable.tablename list the behaviour would be the same as a table
(a refresh there gives you the exact view of the data if it's changed by
another user). It seems not to be so, why? >>

It should do so - are you using the latest release ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I'm using 1.05b1. Tested it again just now and it doesnot work for sure. I
connected the EDBmngr and a little testapp to the same remote db. I deleted
in EDBmngr a record from one of the tables that was part of the view. Then I
refreshed the Tedbtable component (with the view as tablename) in my
testapp. I could still see the record. Stopping and restarting the testapp
again showed the correct result (could not see the deleted record).

Regards, Harry

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:60FD0E8E-7EA6-48E5-947B-BB091C74546E@news.elevatesoft.com...
> Harry,
>
> << Is refreshing a view the same as refreshing a query in the way that you
> only refresh your view of the data locally, so you have to close and
reopen
> tosee actual changes? >>
>
> Not with the latest EDB versions - they allow a true Refresh on queries
and
> views that perform proper change detection and automatically refresh the
> result set as necessary.
>
> << I thought that -although a view is a 'kind' of query-,because you see
it
> in the TEDBtable.tablename list the behaviour would be the same as a table
> (a refresh there gives you the exact view of the data if it's changed by
> another user). It seems not to be so, why? >>
>
> It should do so - are you using the latest release ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Tim,

Tested it with a query and when setting requestsensitive to TRUE then it
worked well. Soit seems that the only thing not working is  refreshing a
view.

Regards, Harry

"Harry de Boer" <harry@staaf.nl> schreef in bericht
news:B6672D6F-6F55-4F3A-B222-6F74CB714BD3@news.elevatesoft.com...
> Tim,
>
> I'm using 1.05b1. Tested it again just now and it doesnot work for sure. I
> connected the EDBmngr and a little testapp to the same remote db. I
deleted
> in EDBmngr a record from one of the tables that was part of the view. Then
I
> refreshed the Tedbtable component (with the view as tablename) in my
> testapp. I could still see the record. Stopping and restarting the testapp
> again showed the correct result (could not see the deleted record).
>
> Regards, Harry
>
> "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in
bericht
> news:60FD0E8E-7EA6-48E5-947B-BB091C74546E@news.elevatesoft.com...
> > Harry,
> >
> > << Is refreshing a view the same as refreshing a query in the way that
you
> > only refresh your view of the data locally, so you have to close and
> reopen
> > tosee actual changes? >>
> >
> > Not with the latest EDB versions - they allow a true Refresh on queries
> and
> > views that perform proper change detection and automatically refresh the
> > result set as necessary.
> >
> > << I thought that -although a view is a 'kind' of query-,because you see
> it
> > in the TEDBtable.tablename list the behaviour would be the same as a
table
> > (a refresh there gives you the exact view of the data if it's changed by
> > another user). It seems not to be so, why? >>
> >
> > It should do so - are you using the latest release ?
> >
> > --
> > Tim Young
> > Elevate Software
> > www.elevatesoft.com
> >
> >
>
>

Harry,

<< I'm using 1.05b1. Tested it again just now and it doesnot work for sure.
I connected the EDBmngr and a little testapp to the same remote db. I
deleted in EDBmngr a record from one of the tables that was part of the
view. Then I refreshed the Tedbtable component (with the view as tablename)
in my testapp. I could still see the record. Stopping and restarting the
testapp again showed the correct result (could not see the deleted record).
>>

Could you send me the database catalog that you're using ?  Just tell me
which view that you're testing with and I can populate some dummy data to
use and try it here.

It should definitely work because we test for this scenario here in our
automated test framework.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Catalog file send to public.binaries: refreshing

Regards, Harry

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:D06C6F56-D6F8-4B5F-852B-CE80984D8903@news.elevatesoft.com...
> Harry,
>
> << I'm using 1.05b1. Tested it again just now and it doesnot work for
sure.
> I connected the EDBmngr and a little testapp to the same remote db. I
> deleted in EDBmngr a record from one of the tables that was part of the
> view. Then I refreshed the Tedbtable component (with the view as
tablename)
> in my testapp. I could still see the record. Stopping and restarting the
> testapp again showed the correct result (could not see the deleted
record).
>  >>
>
> Could you send me the database catalog that you're using ?  Just tell me
> which view that you're testing with and I can populate some dummy data to
> use and try it here.
>
> It should definitely work because we test for this scenario here in our
> automated test framework.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>