🚀 go-pugleaf

"John Moshakis" <john@moshakis.com> wrote in message
news:424237c1@newsgroups.borland.com...
> Vagelis wrote:
>
> >
> >
> >
> > I mean that the error occurs when I press the "Insert" button of the
> > second dbWebNavigator.I get the error message: "Internal Error in
> > Module DBWebGrid2.Invalid CurrentPageIndex value. It must be >= 0 and
> > < the PageCount." and no row is added to DBWebGrid2. DBWebGrid2 is
> > not even rendered on the page. Instead of DBWebGrid2 I get the
> > beautiful error message on my page. Could this probably mean that the
> > problem has to do with rendering of the 2nd dbWebGrid? Or maybe
> > something before the rendering takes place? I'm not experienced
> > enough to judge. But it looks as if the PageCount value of DBWebGrid2
> > is estimated according to the pages needed for the specific record of
> > the master table. So when a new record with no specified foreign key
> > is added in the end of the detail table, PageCount property is
> > exceeded. I would like to catch the exception and check the PageCount
> > value right before the error occurs.Should I implement the OnClick
> > event of DBWebNavigator2? And if this is the actual problem how could
> > I change the PageCount property?
> >
> > Thanks for your interest John.
> >
> > Vag
>
> The onclick of the dbwebnavigator wouldn't be fired when you press the
> buttons. I've never seen the error your getting. What database are you
> using ? You could post an example in the attachments group and I'll
> have a look at it.
>
> Cheers,
> John
>


I'm using MsAccess 97 files to populate my Grids.
But I just came through a paragraph in the .NET Framework Developer's guide
which made me feel quite silly:
"
Unrelated Tables Only
The automatic command generation logic generates INSERT, UPDATE, or DELETE
statements for standalone tables without taking into account any
relationships to other tables at the data source. As a result you may
encounter a failure when calling Update to submit changes for a column that
participates in a foreign key constraint in the database. To avoid this
exception, do not use the CommandBuilder for updating columns involved in a
foreign key constraint and instead, explicitly specify the statements used
to perform the operation.

"
And since CommandBuilder populated my first table easily and efficiently,
when I added the relation and the second table, it never occured to me that
I would have problems. I will try to create my commands without the use of
the CommandBuilder, before wasting more of your time John. I suppose that
the reason of the error MUST be the Insert command generated by the command
builder. If this doesn't work either, I'll post in the attachments group.

Thanks a lot,

Vag

ps "The onclick of the dbwebnavigator wouldn't be fired when you press the
buttons"???Why? Isn't it supposed to do exactly this thing?