Hi,

I'm new to formspider and worked through some tutorials, up to read, delete insert and save REGIONS table. Because of Problems with the REGION_ID( duplicate key ) I implemented a trigger, which works fine. The app did work fine. After naming the buttons ( after one Week not working with formspider ) in the ButtonPanel the app does't work correctly any more. No Commit is working, I can delete or insert rows, api_debug.log's show that all Functions incl. Commit were called, but commit does't not work. There are no Errors shown in the Window. UnNaming the Buttons again did nothing. It seems that the Trial Version disables the api_application.doCommit, but a normal COMMIT also does'nt Work. What could be the problem ?

Thanks

Dirk

asked 21 Aug '15, 08:33

A112's gravatar image

A112
112
accept rate: 0%


I changed the datasource from tabel to query, because I couldn't change the order ( or don't know how ) and inserted then an orderby-Clause. Because I found in an other thread the statement : "It skips datasources that can't be committed (such as datasources that are instances of query based datasource definitions etc...) " , I changed it back to Table, but the problem still remains.

link

answered 21 Aug '15, 09:09

A112's gravatar image

A112
112
accept rate: 0%

Hi Dirk,

Formspider Trial does not have any limitations regarding the doCommit API. When the trial version expires, the Formspider IDE stops working. That is about it.

I'd be very surprised to see if the problem turns out to be that the api_application.doCommit API is not working. If there was any issues with this API, we would have heard about it by now many times over.

One other possibility is that maybe the "Issue DML For" checoboxes are not checked. These checkboxes are in the main screen of the datasource definition dialog. Formspider will not issue insert, update and delete statements unless the corresponding checkbox is checked. Could you verify that these checkboxes are checked please?

Issuing a regular database commit will not have any effect. The modified data in the datasources that Formspider posts (and then commits) to the database are not stored in a transaction in the database session your PL/SQL code is running. So a regular commit will not work. That's normal. (And I know that this is different than how Oracle Forms works.)

Kind Regards,
Yalim

(21 Aug '15, 13:11) Yalim Gerger ♦♦

Hi Yalims,

thanks, the mentioned checkboxes were the reason, I forgot them to reset after changing back from query to table mode( problem must be trivial ).

Dirk

link

answered 24 Aug '15, 04:59

A112's gravatar image

A112
112
accept rate: 0%

edited 24 Aug '15, 05:18

Hi Dirk,

I saw that you removed a question from your reply. It might be that you found out the answer by yourself but I'd like to be sure. You can base a datasource definition on a table and order the results. You don't have to use a view to order the results. There is an order by field in the Query tab of the datasource definition dialog. Actually, this is the preferred method over adding an order by clause to a view.

Kind Regards,
Yalim

(24 Aug '15, 05:37) Yalim Gerger ♦♦

I removed this, because it would be a theme mix. The problem was that the where- and orderby-box were not shown in table mode, only in querymode. I don't know why, today they are shown also in tablemode.

(24 Aug '15, 07:25) A112

Hi Dirk,

Interesting. Actually, the opposite is correct. the where and order by clause fields should show if the datasource definition is based on a table. They should not show if the datasource definition is based on a query.

Kind Regards,
Yalim

(24 Aug '15, 07:49) Yalim Gerger ♦♦
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×9
×6

Asked: 21 Aug '15, 08:33

Seen: 931 times

Last updated: 24 Aug '15, 07:49


© Copyright Gerger 2017