Re: Web enabled forms ( Was: Web enabling Forms 4.5)

From: Richard Leigh <rleigh_at_deakin.edu.au>
Date: Wed, 23 Sep 1998 10:52:15 +1000
Message-ID: <3608463E.EC558BCC_at_deakin.edu.au>


Mark,

Maybe you problems originate from the font which is being used. JAVA has a limited set of fints for use - so if in your Cient Server version of the Forms you are using a non-supported font it may cause problems in the deployment...

Oracle provide a way of substituting fonts - edit the following file on the server

ORACLE_HOME\forms45\java\oracle\forms\uiClient\v1_4 \util\Registry.dat

And setup your font mapping (look for the following line:)default.fontMap.defaultFontname=Dialog If the font you used in development does not map to a java font the above will be used.

Font Mappings:

JAVA                     X-WIND
Courier                   adobe-courier
Dialog                    b&h-lucida
Dialog Input            b&h-lucidatypewriter
Helvetica                 adobe-helvetica
Symbol                   its-zapfdingbats
TimesRoman           adobe-times

Hope this helps,

Richard Leigh

Mark S. Reichman wrote:

> I notice you are talking about web enabling forms. We are having
> some difficulty here and were hoping you could help.
> We are using Designer 1.6,Forms 4.5 on Solaris..
> We will be upgrading to Forms 5.0 and Designer 2+ as soon as possible
> but for now this is what we have. Ok.. We are moving Forms 3.0 (VMS/Dec Alpha)
> to Web enabled Forms 4.5 on Solaris. The 3.0 forms convert
> ok and look and act fine in Designer 1.6. However when viewed through netscape
> on the web the text is out of alignment with the fields. In short, what you
> see in Designer is not what you see on the web. If we misalign the text in
> designer and fool around with the form/fields we can get it to look ok on the web
> but this is getting to be a pain. It seems as though what I see in Desinger is
> exactly what I should see in the web enabled form. There are other problems with
> vertical scroll bars not showing and focus problems also. Is 2.+ Desinger going to
> solve these problems? Are these problems site specific problem or does it exist
> elsewhere? Any suggestions of setup files to look at that will fix this?
> I sure would appreciate any help in this area. Thanks..
>
> In article <36072ECC.C1BA7F51_at_deakin.edu.au>, rleigh_at_deakin.edu.au says...
> >
> >Hiya,
> >
> >You will not need a web application server to do this... Only a version of
> >Developer 2000 server release 1.4 or above... 1.6 or less to support forms 4.5
> >and 2.0 or more to support forms 5.0
> >
> >You will need to regenerate the fmx files on the platform that the "forms
> >server" resides.
> >
> >I highly recommend using Developer 2000 version 2 or higher as there are many
> >limitations problems which you will come accross when web-enabling complex
> >applications.
> >
> >Richard Leigh
> >
> >
> >
> >Avion Consulting & Services wrote:
> >
> >> Does web enabling conventional client-server forms only involve regenerating
> >> the fmb's on a web version of forms? We have a Forms app which we are
> >> looking at web enabling... We sure would need a Web Application Server, i
> >> think. Could someone clarify, pls
> >>
> >> TIA
> >>
> >> Sridhar subramaniam
> >
> >
> >
Received on Wed Sep 23 1998 - 02:52:15 CEST

Original text of this message