Do you provide these things in SQL*FORMS forms (v3.0)

hi there

do you provide any of the following things in your SQL*FORMS. if so then I would like to exchange some ideas, share some problems with you.

0. You do not use default forms because of various problems such as

1. lack of good navigation
2. lack of modes
3. you never know when you will get that "Do you want to commit ?"
4. it is simply insufficient.
5. Forms are multitable, multiblock ,multirecord , multipages
6. Any form gives various modes such as Add, Modify (Retrieve / Delete). once in a prticular mode you may continue to be in that mode. to exit out of a mode you press some key, get a nice menu asking you to 'Accept,cancel or resume' to select operation. and then you may select the new operation. Or any other method such as function keys to select modes.
7. implemented inter-block relationships. i.e field in block 1 is related (in some way) to fields in block 2.

   examples -

	1.in a standard master detail form, the total of purchases made is in
	  master block and the details are in another detail block.

	2. you may want to validate a master field based on detail fields. 
	for which you may have to lop through detail block fields. 
	(but if the master field is mandatory then you can not navigate to 
	detail block for checks). you may also want to validate details based
         on master fields and face similar problems.

	3. you had to use tricks such as set_field(mandatory,off) then 
	navigate to detail block do the checking and then back to master block.

4. tried implementing delete record confirmation at detail and master level

   i.e asking user in menu "Yes","No" before proceding with deletions. but then    you had to use all the tricks because of navigational failures when current    block from which you are navigating is not valid.    i.e did you ever try to navigate out of a detail block which has some    mandatory fields, but you did not want to validate it becuase you wanted to    delete it. (but validation comes first, before deleting)

5. Implemented case insensitive seraches for master blocks. i.e search on

   vendor "Microsoft" and "MICROSOFT" are same.

6. Searches on non base table field. i.e search for all orders where vendor's

   name is 'ABC%'. when vendor name is display only field in the order data    entry form.

If you have tried most of these things, I would like to hear the kind of problems you faced.

Thanks a lot.

Aniruddha kortikar (kortikar_at_mipos2.intel.com) Received on Wed May 13 1992 - 21:17:53 CEST