Skip to Main Content

Oracle Forms

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Tips For Getting the Most Out Of What You Post

Michael Ferrante-OracleNov 9 2020 — edited Jul 6 2023

Forums and social media in general can be a great place to find solutions to technical problems. It can also be a great place to offer feedback about a product or service. However, when posting we sometimes forget to consider that the reader likely does not work with you, does not know your application, does not know your environment, and most certainly is not in your head.

Too often we see posts like this:

“I'm trying to use Forms and it doesn't work. Help me fix it.”

Do you really think anyone can offer any help with such limited information? Probably not. So...

Here are the 10 commandments for forum posters; divided into 5 rules for correct posting and 5 for being a good member of the community.

Five rules to getting a better solution (faster):

1. Have a meaningful subject line.

Subject lines like "I need urgent help" are useless. If your issue is urgent, don't use a free forum to get help. Everyone contributing to the Forum is a volunteer. Contact Oracle Support if you need urgent assistance.

Your subject should specify the problem and not include personal emotion.

2. Give details about versions and technologies.

Are you using Oracle Forms, E-Business Suite, ADF, JD-Edwards, etc? And, exactly what product version(s) are you asking about? Remember that "12c", "10g", "6i" are not product versions. These are portions of a product name and do not accurately represent a technical product version and most times such references are of no value.

3. Give detailed error messages.

Don't say - "it throws an error" - tell us what the error is and give the stack trace and/or full error message text and the number associated with the error.

4. If possible provide steps to reproduce the problem.

If something doesn't work for you - we can't know why if you don't explain what you did (the steps) to expose the failing behavior. When possible, you can even post code that you believe reproduce the problem.

5. Search before you post.

It's for your own good - it brings you the solution faster. It is very likely that your question or some similar question has already been asked and answered. Search both the Forum and Google for your question - you'll be surprised how many times you'll find a solution that someone else got.

Five rules to become a better member of the forum community:

6. Get a name.

In your Forum Profile you can set up a name or handle that will help us recognize you. Be sure to share some of the other details too. Do you really want to be known as user5667847? Using your real name is even better - then when someone meets you in a conference or an event they'll already know who you are.

7. Post the solution.

If your issue was solved, post/share the solution on the thread so others that run into the same error can fix it faster. Just writing "I fixed it" doesn't count.

8. Mark solved problems with [Solved].

Once you found a solution to a problem edit the thread and add [SOLVED] to the subject line. This will help people identify solved problems. Also be sure to mark the post that solved the issue as the "Accepted Solution".

9. Monitor your threads.

In your forum Profile (upper right corner) you can quickly get to Discussion in which you've been involved, either created and/or contributed. This way you'll be able to get better response time and also answer follow up questions.

10. Don't just ask questions - give some answers as well.

The forum is a "community". The community will only grow if we all are active participants. Posting the question is just one side of the coin. Answering other peoples' questions is even more important. Please be a contributor too.

Original post can be found here:
https://blogs.oracle.com/shay/10-commandments-for-the-otn-forums-member

Comments

The language shown in the Forms runtime is the result of your NLS_LANG setting in the runtime environment configuration (e.g. default.env). However, Forms can only change the language of labels it knows about. For example, the ones you highlighted. The column titles, in your example are labels that you elected to use (or column names from the DB). As a result, we cannot change them automatically because we would have no idea if that is what you wanted to do.

You would need to programmatically change those if desired. For example:

SET_LOV_COLUMN_PROPERTY ('LOV1', 2, TITLE, 'Nombre del empleado (Spanish)');

In this example, I am running a form in English but want one column to show in Spanish. So, I use the code above to make that change at runtime.

xu meng Feb 12 2025

Thanks for your reply, your example has inspired me a bit, but it still can't meet my usage needs.
I'm confused about:
When my system language variable is Chinese, I want to make the LOV component's Query/Confirm/Cancel button appear separately in other languages. As shown in the image above.
I don't know, but you can understand what I mean.

xu meng Feb 12 2025

As shown on the picture you provided. "查询" is displayed when the Chinese environment variable is used, and "FIND" is displayed when it is used in English. At present, I want to make the button of its LOV component window display "FIND" separately in the Chinese system, but I have not found the method in the help document and the network.

As I mentioned, strings built into Forms like “Find”, “Ok”, “Cancel”, and others can be translated into the language you choose in the runtime environment using the NLS_LANG settings. Unfortunately, this cannot be changed after the application has been started. So if the app is started with for example, Chinese-Traditional it cannot later be changed to French while the form is running. This means that you must either configure your server to support multiple languages and create modules for each language. This is often the best approach. There are other ways that customers have used, but what I described here likely would require the smallest effort.

You did not mention which Forms version you are using and therefore I cannot point you to the documentation for that version. However, here is the link to the related documentation for Forms 14.1.2. The concepts are basically the same for earlier versions, although some minor improvements have been introduced in the latest release (14.1.2).

https://docs.oracle.com/en/middleware/developer-tools/forms/14.1.2/working-forms/enabling-language-detection.html

But again, for strings that do not natively belong to Forms (you created them) you would need to programmatically change them as necessary.

xu meng Feb 12 2025

OH! I will try to implement your plan first. Thank you for your patience. My Forms version is 11.1.2.

As you are likely aware, but I feel it necessary to mention in case you are not, Forms 11.1.2 was desupported many years ago. I recommend you consider upgrading to the latest Supported version in order to ensure that you can get the latest bug fixes (including security fixes), the latest features, and improvements like what I mentioned about language support and others.

Details can always be found on the Forms product page.

https://www.oracle.com/application-development/technologies/forms/forms.html

xu meng Feb 12 2025

Thank you for telling me this news. I will consider your suggestion carefully and refer to it later. Thank you for your answer.

1 - 7
Locked Post
New comments cannot be posted to this locked post.

Post Details

Pinned by Michael Ferrante-Oracle on Mar 1 2023
Locked on Dec 7 2020
Added on Nov 9 2020
0 comments
2,397 views