Re: WebDB Problems & Workarounds

I found two more Problem Bugs:

1. When you rename a Form in the Component Manger for that form, It doesn't rename the internals in the stored procedure don't rename. This means that the .Accept and .Help procedures are fired off using the original form's name. Workaround is to use the Copy function and then go back and Delete the old form.
2. Frame Driver Problems. When you enter the select on the "SQL Query for Frame Driver" dialog, the second column which is either a HTML/TEXT, URL, or PL/SQL statement, the WebDB parser won't allow the statement to be saved yeilding many errors. This happens when the 'this is what is in the second column' exceeds 34 to 36 charactors in length. If there is a "_" or "." in this string, then it will fail at a shorter length. Workaround: Enter a dummy string 'Dummy String 001' then search for it in the stored procedure after saving and edit the stored procedure replacing it with the appropriate string values. Note that you'll see the string in ''Dummy String 001'' the double quotes must remain in the stored procedure's coode.

Does Anyone know how to report such bugs to Oracle and if Oracle has released any SQL files to patch these type of bugs???

-Brooks

Brooks Vaughn wrote:

> Some of the tihings I have been faced with are:
>
> 1. When entering code (for Forms edit) into the On Successful Submitt,
> gives a Java Script error when you try to edit that form again. I have
> to revert back to a archive version and reenter the code to make changes
> to the form.
>
> 2. When using Unstructured Forms, undesired resluts can occur with using
> LOV's and ComboBoxes. Must use Structured forms instead.
>
> I'm still having problems with the basics like:
>
> 1. How to call components from other components
> 2. How to return to a previous form or report after calling another
> form,
> 3. How and where to HyperLink the day of the month on a canendar to a
> insert calendar event form
> 4. etc...
>
> -Brooks
>
> >>> Jacquie Armstrong <jacquie_at_softtracks.com> 02/24 12:40 PM >>>
>
> That would be great... I know that in the past couple of days I have
> fought with WebDB only to discover things like:
>
> 1) when writing a report based on an SQL Query you CAN'T put a
> semi-colon at the end of the query
>
> 2) If you want to tell who is logged on to the system (in order to
> restrict the data they see), you must change the DAD settings so that
> WebDB components use the secure DAD. (Otherwise the user of the
> component is the PUBLIC user)
>
> 3) There is no way to add joins to a query if you have created it using
> the Wizard. (Our standard is now to create all reports from our own SQL
> queries)
>
> It would be very helpful if we could bounce ideas and problems off each
> other.
>
> Thanks, Jacquie.
Received on Fri Feb 25 2000 - 08:30:34 CST