New version of SAOUG FldEdit program available...

First, we would like to announce the newest version of FldEdit. It fixes a problem identified with the 30 character "Application Title" field. In our environment, all application titles are 8 characters long, so we naturally assumed that 30 character was more than enough. We have changed this to reflect that actual size of the field (80 characters). A copy of the E-Mail that Ms. Greeder sent to the person who found there error is enclosed:

Thank you for your comments and suggestions concerning the FLDEDIT Form. Your problem with the 30 character "Application Title" field has been taken care of. I edited the form and changed the "Field Length" and "Query Length" to 80 characters (this is the max we can go). I left the "Display Length" set to 26 in order to maintain the form's original appearance, but it is now a scrollable field. This will eliminate your "Fieldvalue truncated blablablabla" error.

In switching to Oracle Ver 6 we found that many of the procedures which ran fine from POST-CHANGE triggers in Ver 5 are now restricted procedures which can't be run from a POST-CHANGE trigger in Ver 6. The reason the open cursor procedure is called from the PRE-RECORD trigger is because it was one of the best ways we found to get around this "restriction". This has been especially painful during our conversion of existing Ver 5 forms to Ver 6 as many of the V2 triggers were disabled by this. If you have found a better way to solve or get around this problem, PLEASE let us know.

Thanks!

Michele

  In other developments, Michael Short, of Oracle Corp. wrote to remind us that the table that we are modifying with the form are not guaranteed to be stable. I have enclosed part of the letter that Mr. Short forwarded. We agree with his statement and have included a caveat similar to the one that he recommends in our documentation.

>From: "Michael Short" <MSHORT_at_us.oracle.com>
>
>Michele,
>
> I've seen several of the interesting bulletins that you have posted.
>With regards to the one below, I encourage you to include a caveat note since
>Oracle Corp. does not support the modification of the underlying SQL*Forms
>tables except through SQL*Forms (Design) or (Convert). See the SQL*Forms
>Designer's Reference, p. 24-4:
>
> The table descriptions are provided for your information. You
> can write reports based on this information or change the
> contents of the tables through SQL*Forms. Do *not* manipulate
> these tables through SQL*Plus.
>
> By including a caveat, you will ensure that readers of your bulletin
>will understand the ramifications of their use of your technique.
>

  Once again, the form is available via anonymous ftp from hrd769.brooks.af.mil. Questions, comments, and suggestions can either be mailed directly to Ms. Greeder at "GREEDER_at_EIS.BROOKS.AF.MIL", or can be posted to the local Oracle Users Group newsgroup mail entry point "saoug_at_hrd769.brooks.af.mil".

-- 
------
TSgt Dave Burgess
NCOIC AL/Management Information Systems Office
Brooks AFB, TX