🚀 go-pugleaf

Gelein van de Voorde wrote:
> Jeff Overcash (TeamB) wrote:
> 
>> Should work, but I've never tried it.  TIBTable is so rarely the
>> correct component in C/S work I have never used it in any kind of
>> environment even quick tests.  Only when someone reports a bug in it
>> do I drop one of those on a form.
> 
> Jeff,
> I can't get it to work. In objectwindow when the data of an updatable
> view is displayed using the TIBTable component you can not add, modify
> or delete records. I already took a look in the IBTable source. What I
> understood from it you disable editing of system tables and
> multitables(views) in InternalGetUpdatable.
> 

Well it might not work.  I do no work on IBTable except for bugs.  I will not be 
adding features that make it more likely people will use it since it is a poor 
choice in almost all situations.  For Views all the fields come back as read 
only even with triggers on the view.  This means I have to do more work to 
determine views and determining what fields actually map to a real underlying 
field.  This would greatly slow down the component.  It won't be changing it wrt 
views.

-- 
Jeff Overcash (TeamB)
       (Please do not email me directly unless  asked. Thank You)
And so I patrol in the valley of the shadow of the tricolor
I must fear evil. For I am but mortal and mortals can only die.
Asking questions, pleading answers from the nameless
faceless watchers that stalk the carpeted  corridors of Whitehall.
              (Fish)