Forms 6i and template.fmb form causes ros error -200

hi.i am trying to create a custom form...i copied the indicated plls and the template.fmb and the appstand.fmb to my client machine...i set the registry for forms60_path to point to this area...now i try to open the template.fmb form and get ros error: -200...don't get anything else...????what am i missing?

Try ROS ERROR -200 / FRM-10081 / PDE-PER001 Internal error (depep 8) - Help appreciated

Similar Messages

Unable to Open a Form - ROS Error : -200

I am not able to open a fmb. i gives me the error message...
ROS ERROR: -200

hi, from METALINK
FRM-10043 Cannot Open File [ID 32968.1]
Modified 11-DEC-2009 Type BULLETIN Status PUBLISHED
Applies to:
Oracle Forms - Version: 6.0.8 to 10.1.2
Information in this document applies to any platform.
Checked for relevance 2-DEC-2009
Purpose
Troubleshooting FRM-10043 Cannot Open File
Scope and Application
Developer
Troubleshooting FRM-10043 Cannot Open File
General Error Description
FRM 10043 Cannot Open File
A.) Migration & Upgrade Problems
1.) Upgrading SQL*Menu 5.0 menus to Oracle Forms 4.5 menus and am receiving FRM-10043 "Cannot Open File" using f45gen.
Solution Description
Make sure Version to Upgrade = 50 is specified in addition to "Upgrade 3.0 Form, 5.0 Menu ..." when using f45gen.
2.) FRM-10043 Cannot Open File when upgrading Designer generated Files
Problem Explanation
The upgrade process does not correctly handle recursive procedures or stacked canvases with right justified fields residing in libraries. The procedure which was appearing twice was mutually recursive with a second procedure.This was not supported / allowed in Forms 3.0 but it worked and isn't supported and allowed in higher formsversions.
Solution Description
The solution was to strip out all the procedures from libraries, upgrade, and copy the procedures back over a block at a time, padding any right justified fields on stacked canvases.
3.) FRM-10043: Cannot open file when upgrading SQL*Forms 2.3 to Oracle Forms 4.5 using f45gen .
Solution Description
Make sure the 'Upgrade 3.0 Form, 5.0 Menu, or 4.0 Module to 4.5 Module?' Forms 4.5 Generator option is checked. This corresponds to the 'Upgrade' keyword used on the f45gen command line.
Example
Use the following Oracle Forms 4.5 Generator Options to upgrade the 2.3 Form: FILE: < Name of Forms 2.3 .INP File > USERID: < Database User Name > PASSWORD: < Database Password for User Name > DATABASE: < Database Connect String > MODULE TYPE: FORM MODULE ACCESS: FILE UPGRADE 3.0 FORM: [X] CHECKED VERSION TO UPGRADE 23 From the command line, use: f45gen form23name.INP scott/tiger upgrade=yes version=23 module_type=form module_access=file
4.) FRM-10043: CANNOT OPEN FILE when upgrading a Sql*forms 3.0 to Forms 5.0 or 6.0
SOLUTION Description
This feature is not supported in Oracle Forms 5.0 and 6.0. The Forms 5.0 online help says: ""Note: To upgrade a version 3.0 or 4.0 form, you must first convert the form to version 4.5, and then convert the version 4.5 form to version 5.0."
5.) FRM-10043 Cannot Open File when upgrading Menus within Forms 4.5 to Forms 5.0.
Problem Explanation
By setting the flag: Upgrade to PL/SQL from V1 to V2, it caused the upgrade to fail and get the 'FRM-10043 Cannot open file' error.
Solution Description
When you are upgrading from the command line or using Forms Compiler, you should have the menu name in all lower case, and if you do this, make sure you have the extension in the same case.
Example
cl_info_menu.mmb NOT.... CL_INFO_MENU.mmb 6.) FRM-10043 Cannot open file ORA-00600: internal error code, arguments: [17289], [1041], [0x402F44C0], ORA-00600: internal error code, arguments: [17281], [1041], [0x402F44C0], ORA-21779: duration not active when compiling a menu
Problem Explanation
Usage of PLSQL deprecated feature in menu trigger or you are upgrading a 5.0 SQL*Menu menu module to Forms9i/10g created this error.
SOLUTION Description
While compilling use UPGRADE_PLSQL=YES
Example
f90genm.sh module=mymenu.mmb module_type=Menu userid=scott/tiger@cs upgrade_plsql=Yes
B.) Problems Opening Modules
1.) ORA-12203 TNS: unable to connect to destination and/or FRM-10043: Cannot open file and/or ORA-1005: null password given; logon denied by double clicking (opening) the file.
Solution Description
Windows File associations if created automatically by the OS do not enclose a command correctly in quotes. This means that any spaces that are included in your filename or path are interpreted by the OS when passed as parameters. Remove any spaces from the path or filename.
Example
c:/Dependency Analysis/mylib.pll change to c:/DependencyAnalysis/mylib.pll
2.) FRM-10044 Cannot create file, FRM-10043 Cannot Open File on opening file in Forms Builder 6i or 9i if directory name contains Umlauts (vowels)
Solution Description
Don't use umlauts/vowels in the directory name
3.) FRM-10043 : Cannot open file in formbuilder an fmx,mmx,.. (You tried to open a file that is not a valid Oracle Forms design module file)
Problem Explanation
This error occurs when you attempt to open an Oracle Forms form, menu "executable file"
Solution Description
You must open the Binary ( Design ) format of the module. You can open the Form .FMB, Menu .MMB and Library .PLL binary files using the Oracle Forms Designer. If you have a text version of the module, you must first convert the text format back to binary format to open the module using the Oracle Forms Designer. The following shows the file extensions for each type of module and storage format.
Text: FMT,MMT, PLD
Designtime: FMB, PLL, MMB
Runtime: FMX, PLL or PLX, MMX
4.) FRM-10043 : Cannot open file in formbuilder if binary file may be corrupt
Solution Description 1
Transfer the .FMB, .MMB or .PLL file again in BINARY mode, and you will be able to open the file using the Oracle Forms Designer.
Solution Description 2
A module which has been worked on before, but suddenly cannot be opened in the Oracle Forms Designer may indicate that the file is corrupt.
Tests
1. Revert to a backup copy of the Oracle Forms file
2. Open the module from the database, if the module had been saved to the database. You can then use FILE->SAVE AS to save the form to the filesystem.
3. Convert from Binary format to Text Format, and then back to binary format.
Reasons
A form can get corrupted due to a number of reasons, including: A series of changes made to the module in the Oracle Forms Designer could have corrupted the form as a result of some bug The file system might not have had enough disk space to save the module The module could have been transferred over a network, and corruption occurred
5.) FRM-10043 : Cannot open file in formbuilder for upgrade .pld files
Solution Description
Upgrading .PLD files is not supported. When upgrading PL/SQL libraries created in Developer/2000 release 1.X, you must convert all .PLD files to .PLL format before you attempt to open them in Developer/2000 Release 2.0.
6.) FRM-10101 : Cannot generate module or FRM-10043 : Cannot open file for modules saved in the database.
Problem Explanation
FRM-10101 occurs when you try to generate a module that is saved in the database and specify extract=yes, or select "Extract module from database into file?" in the Generate Options dialog window. FRM-10043 occurs when you try to generate a module that is saved in the database, but do not specify extract=yes.
Solution Description
The module name is case-sensitive. When modules are saved to the database, the module name is saved in uppercase.
Example
You have saved a form with module name "mm" to the database.
Using Generate from the command line:
f45gen module=MM userid=scott/tiger extract=yes not f45gen module=mm userid=scott/tiger extract=yes
Using the "Generate Options" dialog window:
File: MM Userid: scott/tiger Module type is FORM,MENU or LIBRARY? Select FORM from poplist Module Access is FILE or DATABASE? Select DATABASE from poplist not File: mm Userid: scott/tiger Module type is FORM,MENU or LIBRARY? Select FORM from poplist Module Access is FILE or DATABASE? Select DATABASE from poplist
Problem Description
This error occurs when you attempt to open a form from the database. Access to the form was granted to the user by the form's creator through: FILE->GRANT->MODULE ( Oracle Forms 4.0.x ) or FILE->ADMINISTRATION->MODULE ACCESS ( Oracle Forms 4.5.x ) and the user name given was public.
Solution Description
Run the grant script to grant access to the Oracle Forms 4.x base tables. Grant access to either the user who is unable to open the form, or to PUBLIC. PUBLIC will allow all users access to the Oracle Forms 4.x base tables.
Examples
Forms 4.5.x (run the script frm45grt.sql as SYSTEM and Forms 4.0.x (run the script frm4grnt.sql as SYSTEM).
7.) FRM-10043 CANNOT OPEN FILE for modules attached libraries or subclassed objects from other modules
Solution Description
- Remove the hard coded path. (For libraries: reattache libraries without path, delete the non portable path). - Check if the library or the other modules are in FORMSNN_PATH. - Check if the env variable for FORMSNN_PATH contains more than 255/512 characters. If yes you can use ORACLE_PATH additional for searching files. (NN could be 40,45,50,60,90)
References
Bug:1317608 WEBFORMS FORMS60_PATH LONGER 512 BYTES DOESN'T RETRIEVE THE FMX
8.) FRM-10043 : Could not open ...olb
Problem Description
Form refers to OLB library with full path. Forms Builder stores full path of opened Object Library in preferences file and will ignore FORMS60_PATH
Solution Description
1. Open Developer preferences file file in any text editor. On Windows preferences file name is CAUPREFS.ORA and is located direcly in ORACLE_HOME folder. On Unix, preferences file is prefs.ora and is in unix user's home folder. 2. Find "Forms.obj_lib_file" entries and remove path info from library file names. 3. Next time Forms Builder starts, it will search for OLB files using FORMS60_PATH.
9.) FRM-10083 : Cannot find/open module for referenced objects. FRM-10043 : Cannot open file.
Problem Explanation
You receive this error trying to open a form in the Oracle Forms designer. The form you are trying to open has referenced objects. The Oracle Forms designer cannot find the source module in the filesystem that contains the definitions of the referenced objects.
Solution Description 1
FRM-10083/FRM-10043 occur because Oracle Forms cannot find the source module in the filesystem that contains the definitions of the referenced objects. If the source module is saved in the filesystem, Oracle Forms uses the following default search path to find the source .fmb file:
1. If the Full Pathname is specified, use that and no other. If you chose Keep Path when you created the referenced object, the complete directory path of the source module would be in the Reference Source Information in the target module. Thus, you must ensure that the source .fmb file can be found in that directory.
2. If Remove Path was chosen, no directory path is specified in the Reference Source Information in the target module. When Oracle Forms needs to locate the source module to read the definition of a referenced object, it looks for the module in the default search path. Oracle Forms will search for the source .fmb file in the following order: a. The Working/Current Directory ( In the icon property for the application on Microsoft Windows ). b. Sequentially in each of the directories named by the value of the environment variable FORMS45_PATH c. Sequentially in each of the directories named by the value of the environment variable ORACLE_PATH
Solution Explanation
When you create the referenced object, Oracle Forms informs you "It is recommended that the fully qualified path be removed."
Solution Description 2
If you have upgraded from a previous version of Oracle Forms, make sure the Reference source form has also been upgraded, before trying to open the referencing form.
Solution Explanation
All applications that are used as the source for references must be upgraded first, followed by upgrading any applications that make references to these source forms.
10.) ROS Error : -200 FRM-10043 : Cannot open file. FRM-11009 : Failed to load color palette.
Solution Description
Make sure that the directory path for the color palette file name is specified, and the file extension is .pal. Also make sure that this file still exists in the file system, and is readable. To check the color palette name and mode that the designer/builder is using: EDIT->PREFERENCES menu or TOOLS->OPTIONS menu The Color Palette field specifies the name of the Oracle Forms color palette that is automatically loaded when you create a new form. If there is any information typed in this field, Oracle Forms will interpret this as a .pal color palette file that must exist in the file system. If this field is blank, the Oracle Forms default color palette is loaded. Thus, if you are not using a custom color palette, this field should be blank.
Solution Explanation
The Oracle Forms designer/builder uses the color palette as specified in the designer preferences or options field to set the visual attributes for the form you are trying to open. If this color palette file is not found or cannot be read, then the ROS and FRM-10043 errors will occur when you try to open form.
11.) Using f60genm to regenerate a form, you get frm-10043: Cannot open file in the .err file and: X Error of failed request: BadPixmap (invalid Pixmap parameter) Major opcode of failed request:54 (invalid Pixmap parameter)
Problem Explanation
You are using AIX 4.3.1 or higher, and the libXt.a file from that OS version is not compatible with Oracle Forms 6.0.
Solution Description
Copy the library file libXt.a (generally in /usr/lpp/X11/lib/R5) from a pre-AIX 4.3.1 O/S (such as 4.3.0) to a directory that won't overwrite your current OS libXt.a file. The $ORACLE_HOME/lib directory is a good place. Set environment variable $LIBPATH to point to that directory. If the customer does not want to copy single file, have them install the following file set from their IBM vendor: X11.compat.lib.X11R5 4.3.0.0 COMMITTED AIXwindows X11R5 Compatibility Library, and set $LIBPATH to include /usr/lpp/X11/lib/R5 instead of the default OS motif libraries.
12.) FRM-10043 : Cannot open file on Apple
Problem Description
see Note:38213.1
13) FRM-10043 : Cannot open file and Form not created If you try to compile a .pll in frmcmp.exe or frmcmp and use the default moduletype=FORM you receive the error.
Solution Description
You have to use Module Type = LIBRARY for .pll or MENU for .mmb or FORM for .fmb

[Solved] ROS ERROR: -200

I created a shortcut to Forms 6 and I put in "Start in" slot the folder where I have the fmb.
When I try to open a form, I get a "ROS ERROR: -200" and then Forms 6 has a fatal error and closes.
Edited by: Danicela on 22 avr. 2009 05:29

Other sources of this error might be you've created mmb etc with different version of forms developer and the current fmb with some other versions.
Make sure that ORA_NLS33 is set correctly before generating:
e.g.
setenv ORA_NLS33 ${ORACLE_HOME}/ocommon/nls/admin/datad2k

ROS ERROR: - 200

Hi,
I am facing a serious problem when I am trying to open one form I am getting an error message "ROS ERROR: - 200" and form is not opening, after that form builder is closed.
I am using Oracle Developer Suite - ora10.
Prasanta.

I think Tony is right,
Try
A work-around is to create another form, and copy every object from the original form to the new form.
The copy is some way "cleans up" the problem

ROS ERROR: -200 while opening a form

I am not able to open a fmb. i gives me the error message...
ROS ERROR: -200

I dont think this is the issue as i have more than 20 GB free space.
I have this feeling that their might me Version mismatch issue.. like
the new form is Build on Oracle 10g version and i am trying to open in forms 6i..
This could look to me the possible cause..
Suggest?

Differences between Ant launched and JDev launched JUnit causing an error

I've got a JUnit test which tests a web service. The test runs fine when launched in from JDeveloper but when launched from an Ant script I get:
[junit] oracle.fabric.common.PolicyEnforcementException: Action header is required when addressing is enforced
[junit] javax.xml.ws.WebServiceException: oracle.fabric.common.PolicyEnforcementException: Action header is required when addressing is enforced
[junit]      at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:749)
[junit]      at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:226)
[junit]      at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:97)
[junit]      at oracle.j2ee.ws.client.jaxws.WsClientProxyInvocationHandler.invoke(WsClientProxyInvocationHandler.java:216)
[junit]      at $Proxy30.process(Unknown Source)
[junit]      at ca.jea.penfax.command.AddANewHireCommand.startBusinessProcess(AddANewHireCommand.java:30)
[junit]      at ca.jea.penfax.command.AddANewHireCommandTest.testStartBusinessProcess(AddANewHireCommandTest.java:27)
[junit] Caused by: oracle.fabric.common.PolicyEnforcementException: Action header is required when addressing is enforced
[junit]      at oracle.j2ee.ws.common.addressing.ClientWSAddressingInterceptor.processRequest(ClientWSAddressingInterceptor.java:166)
[junit]      at oracle.integration.platform.common.InterceptorChainImpl.processRequest(InterceptorChainImpl.java:91)
[junit]      at oracle.integration.platform.common.mgmt.InterceptorChainManager.processRequest(InterceptorChainManager.java:216)
[junit]      at oracle.j2ee.ws.client.mgmt.runtime.SuperClientInterceptorPipeline.handleRequest(SuperClientInterceptorPipeline.java:96)
[junit]      at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:532)
[junit]      at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:510)
[junit]      at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:701)
The error occurs on the line that invokes the webservice. What parameters is JDeveloper setting up that I need to replicate in my Ant script? Is there a way to use the JDeveloper TestRunner instead if it will cause me fewer problems?

851004 wrote:
..It has been re-written from spec="1.0" to spec="1.5" ..Who changed it, and why?
..Does anybody else have an answer, solution, or suggestion ..?I suggest:
<ul>
<li>Change the spec. number back to something that 1.4 JWS claims to understand (i.e. "1.0").
<li>Checking the launch file using JaNeLA
</ul>
Edited by: Andrew Thompson on Apr 9, 2011 7:54 AM

Opening Region, Page and Business Component XML causes unusual errors.

Hi
I'm a bit new to extending E-Business Suite, so apologies if this is a bit unclear.
1. I have set up JDeveloper according to the docs and that seems OK
2. I have copied the entire oracle/apps/icx java tree from $JAVA_TOP
3. I have exported all /oracle/apps/icx PG and RN xml files
Now when I try and open a PG.xml I get a load of the following errors:
Invalid value "/oracle/apps/icx/lov/webui/UnNumberLovRN" for property "External LOV" on component "/oracle/apps/icx/por/req/webui/CheckoutSummaryPG.UnNumber". Component "/oracle/apps/icx/lov/webui/UnNumberLovRN" cannot be referenced from "/oracle/apps/icx/por/req/webui/CheckoutSummaryPG.UnNumber" because it violates scope restrictions.
I also have a problem importing Business Components. When right click on the jpx and select "Import Business Components", then select my server.xml file, I get the following error:
"Unable to import package. This is not a valid Business Components XML file."
Am I doing this wrong or is there something afoot?
I am using JDeveloper: 9.0.3.5 Build 1312 from the patch
We are on 11.5.10.1 plus some patches.
Any help most appreciated!!!
Thanks
Chris

you can ignore the warnings you get for the page xml files.
You need to mention which version of jdev are you using ? Did you try opening the server.xml directly ?

ROS Error while saving form

Hi,
When i am saving a form it is giving the following error :
ROS Error: -200
I dont understand where the problem is.
My forms version is 6.0.8.24.1
Any help in this regard is highly appreciated.
Thanks in advance.
Venkat.

I got the solution. I just exited from the forms and reopened the form again.
Now it is allowing me to save.
I dont know the funda behind this.. Anyhow my problem got solved.
If any one knows the resson please post it.
Regards,
Venkat.

Help: Attach library to template.fmb

Hi,
We have a set of Forms uses a single template.fmb. The template.fmb has an attached library say, app.pll. We recently add some new procedures in the spec and body of app.pll. It turned out that these changes messed the library procedure call.
We dropped the attached library from the template.fmb and attached app.lib to the FORMS with the issue. It worked and it uses the changes of the updated app.pll.
Question:
1. Does this mean that we should not attach library to template.fmb?
2. Should we re-compile all existing FORMS that use the template.fmb?
Any suggestions are greatly appreciated.
Thanks in advance.
Jimmy

Andreas Weiden wrote:
If you add procedure and or funtions to a package in your lib, you should add them at the end of the code. Hi Andreas,
I further checked the situation and only found that there are couple of more .pll files at various locations of different versions within compiling scope.
1. I renamed they all and left only the latest one.
2. Put .pll and template.fmb together in lib directory within the compiling pass.
It turned out the way of code change need not be at the end of the code.
Thank you again.
Jimmy

Edit template.fmb to incorporate my custom forms

Hi guys,
I have created 2 forms on my win xp workstation using Forms 6i Builder, both of which work fine. Now i want to install them into the
oracle application on our server (which runs on linux platform). Copied template.fmb, appstand.fmb, the libraries and changed the the
FORMS60_PATH registry to match the folder with the libraries. I can open/compile the template form without any errors or problems.
As far as i understood i have to incorporate them in the template.fmb but i wasnt able to do this. Tried to copy each object from my forms
in the object lists of template.fmb but when i was opening the canvas all elements were piled up in the top left corner of it and were scaled to tiny sizes.
How exactly do i go from here? Just to remind you i have 2 forms so i have to go through the process twice.
i have just tried something else. I have copied the objects from my forms to a new blank form and it works. But with template.fmb
everything is messed up.
Thanks,
Iulian
PS: Sry if this is the wrong branch, i've just been told to post in the E-business Suite.

So basicly you are saying this :
1. I can just as well compile my forms on the server as they are and they would work but it wouldnt follow the recommended standard.
2. What i did is just circling the bullseye.. in other words i didn't use the template as intended. If this is true please tell me how to actually edit the template.fmb to bring in the content that i have already created. I have read other threads about this and none explained this issue.
A quick step by step would help.
Right?
Thanks Kiran!
So this question remains open for the moment.
Edit: going home now, will answer tomorrow.
Edited by: iulianB on Feb 22, 2010 8:01 AM
Edited by: iulianB on Feb 23, 2010 2:30 AM

How to use template.fmb file within form builder

Hi
I have created forms without using template.fmb file
and deploy them on EBS then they working fine
But when I try to use template.fmb file then it gives an error
following are the steps :
1:open template.fmb file with form builder
2:rename that file with XXXX.fmb
compile that file and deploy XXXX.fmb file in AU_TOP
after that
in putty i m trying to create XXXX.fmx file in same TOP but it gives an error
Forms 10.1 (Form Compiler) Version 10.1.2.3.0 (Production)
Forms 10.1 (Form Compiler): Release - Production
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
PL/SQL Version 10.1.0.5.0 (Production)
Oracle Procedure Builder V10.1.2.3.0 - Production
Oracle Virtual Graphics System Version 10.1.2.0.0 (Production)
Oracle Multimedia Version 10.1.2.0.2 (Production)
Oracle Tools Integration Version 10.1.2.0.2 (Production)
Oracle Tools Common Area Version 10.1.2.0.2
Oracle CORE 10.1.0.5.0 Production
Compiling package specification APP_CUSTOM...
No compilation errors.
Compiling package specification APP_CUSTOM...
No compilation errors.
Compiling package body APP_CUSTOM...
Compilation error on package body APP_CUSTOM:
PL/SQL ERROR 302 at line 22, column 19
component 'DISABLED' must be declared
PL/SQL ERROR 0 at line 22, column 5
Statement ignored
PL/SQL ERROR 201 at line 40, column 5
identifier 'APP_WINDOW.CLOSE_FIRST_WINDOW' must be declared
PL/SQL ERROR 0 at line 40, column 5
Statement ignored
Compilation errors have occurred.
Form not createdfollowing is command
$ frmcmp_batch module=$AU_TOP/forms/US/XXXX.fmb userid=APPS/apps output_file=$AU_TOP/forms/US/XXXX.fmx module_type=form batch=NO compile_all=special

for you question - EBS General Discussion General EBS Discussion
Compiling Forms In R12
and search on forum

Template.fmb error with Forms 9i

Hi, please could someone explain how the following error can be solved.
I have been given a Form as an .FMB file which I need to modify slightly and then compile to an .FMX file. However when I load the .FMB file into Forms Builder 9i an error dialog appears containing the message:
FRM-18108: Failed to load the following objects.
Source Module:Template.fmb
Source Object: WHEN-NEW-FORM-INSTANCE
Source Module:Template.fmb
Source Object: WHEN-WINDOW-CLOSED
etc, etc, etc.
This is followed by a second error dialog stating:
FRM-10102: Cannot attach PL/SQL library Form. This library attachment will be lost if the module is saved.
FRM-10102: Cannot attach PL/SQL library Company. This library attachment will be lost if the module is saved.
Can someone please explain this? I can find no trace of a file called 'Template.fmb' anywhere on my machine!
Many thanks for your help. I will be very grateful for any clues!
Terry.

Thanks for your reply Professor Yaffle. Originally I assumed that 'Template.fmb' (plus other library files) must be something specifically developed by the people who gave me the .FMB source file, however I then did a search with Google and came across several references to a file called 'Template.fmb' (usually in the context of an older version of Forms, 6), which suggested that this file may be a generic Oracle file which ships with Forms (or an old version of Forms).
Unfortunately none of the hits that I obtained with Google were particularly useful in telling me what this file is or where I can get a copy (if it is a generic publicly available file). There were several comments along the lines of, "download files from the $AU_TOP/resources directory to your local disk", but what is $AU_TOP?
I am now beginning to think that perhaps 'Template.fmb' really is something that was developed by the people who gave me the .FMB source file, as you suggest.
By the way Professor Yaffle, I see that you are in Bath, UK which, by coincidence, is only about 14 miles north of where I am (Frome)! Small world, as they say.
Terry.

TEMPLATE.fmb: Custom form can't display any system message

I was using the template.fmb to create a new custom form. It works fine, BUT it can't display any system message such as ""FRM-40400 Transaction complete: 1 record applied and saved"
Please advise what's the problem.
Thanks

use something like this
:System.Message_Level := '10';

How to develop forms using TEMPLATE.fmb

hi,
Anyone Should suggest me clear tutorial/links to learn forms development using TEMPLATE.fmb with step-by-step development procedure including forms development, register in apps.
Thanks in advance.

Abdetu is right, General EBS Discussion is the more appropriate forum for this question. Having said that, creating a new form based on the TEMPLATE.fmb just ensures your EBS Custom form has all of the basic EBS requirements for a EBS form. Developing for the EBS Framework has many requirements and I strongly recommend you review the Oracle Applications Documentation library. Select your EBS version and then scroll to the Standards section and review the following documents:
<ul>
<li>Oracle Applications Developer's Guide
<li>Oracle Applications User Interface Standards for Forms-Based Products
<li>Oracle Application Framework Personalization Guide
</ul>
If you are looking for general "Forms" tutorials, here are a few good links. Although a few of the following links are for older Forms versions, the concepts are still valid across all Forms versions.
<ul>
<li>A Tutorial on Oracle9i Forms and Reports
<li>Tutorial for Oracle10g Forms / Reports
<li>iSelfSchooling - Basic Introduction to Forms
<li>Oracle Forms 10g: Demos, Tips and Techniques
</ul>
Hope this helps,
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.

BLOCKNAME data block from TEMPLATE.fmb displaying when I close my form

Hi all,
I'm developing a custom form in EBS, and when I close my form using the X button, the BLOCKNAME window from TEMPLATE.fmb is displayed. If I close using File -> Close Form, I get the expected behavior.
Does anyone have any suggestions for how to fix this?

Hi,
I've still been unable to make any progress with resolving this issue. Does anyone have any suggestions?

Forms 6i and template.fmb form causes ros error -200

Similar Messages

Maybe you are looking for