Re: Forms and commit

Try replacing the commit_form; statment with forms_ddl('commit');

Mike

"Scott Mattes" <ScottMattes_at_yahoo.com> wrote in message news:CxHx7.2144$M6.573191_at_news1.news.adelphia.net...
> Ah, no, I can't post it, but I can tell you what it is doing (I know, not
> the same thing, but...).
>
> The form comes up, user selects an action from a radio group, goes to that
> canvas (none of the fields are linked to the database, they are strictly
for
> data entry and display), enters data, clicks on the submit button and the
> data is taken and put into the DB via 'insert into tablename fields(
> field_list ) values( value_list);' and after 13 records are insert it does
a
> commit and then a go_block to return to the first canvas. I stepped
through
> it in debug and every insert happened, the commit happened and the
go_block
> happened, then the procedure was exited - all with no exceptions raised.
> What I saw afterwards was 1) no new records in the DB, and 2) the wrong
> canvas displayed.
>
> If I take out the commit I still get problem #1, but problem #2 is cured.
>
> Someone sent me an email directly in which was stated that Forms
determines
> the need to do the commit and if it feels it isn't needed it doesn't
really
> do it. I can accept this, though I don't like it - it means processing
hoops
> that have to be jumped through that aren't needed if the tool behaved
> itself. What I don't understand is the wrong canvas being displayed.
>
> I am in the midst of trying to define a block that is linked to the table
> fields, but to do a create_record at least one of the fields needs to be
> navigatable. I don't want these to be seen by the user. I then moved those
> fields to the block that has the input fields, but now I have to save off
> the input values for use in the insert statements, because every
> 'create_record' also makes new versions of the input fields.
>
> What is the 'right' way to do this? I would, actually I did, think that
> using the 'insert into table...' should be the way to go.
>
>
> Thank you for any light that you may be able to shed on this problem.
>
>
>
> "Matt B." <gtimatt_at_home.com> wrote in message
> news:l0Cx7.56954$Xk4.4189103_at_news1.rdc1.sdca.home.com...
> > "Scott Mattes" <ScottMattes_at_yahoo.com> wrote in message
> > news:Hdsx7.791$M6.346659_at_news1.news.adelphia.net...
> > > Forms 6.0.8.12.1
> > >
> > > I thought I was going nuts, but I have narrowed it down to the commit
> > > statement. With the commit working, not only are my inserts not
> commited,
> > > but Forms completely ignores my go_block and goes to a canvas that is
> 'near'
> > > where i want, but is not the one I want.
> > >
> > > I have checked for other triggers that might be getting in the way,
but
> I
> > > haven't found any. The when-new-block-instance trigger for the block i
> want
> > > to go to does not fire after the trigger that contains the 'commit;
> > > go_block'.
> > >
> > > I think it is time to shut down and think of something else.
> > >
> > > Any help would be GREATLY appreciated.
> >
> > Can you post your code for us to see?
> >
> > -Matt
> >
> >
>
>
Received on Mon Oct 15 2001 - 03:34:44 CEST