Re: Code designer bugs - are there fixes for these problems?

[Jim Essinger <esinger@xxxxxxxx>]

Mike,

The point is that designer fills in the REFFLD stuff in the first
place.  All I do is go to a physical file to insert a field for a display.
(Right click>insert Field>Database Reference, then follow the prompts)
Designer is doing all the work, but somewhere it is doing it wrong.  I'm at
home now, but I will look again at the source it creates when importing a
field from a field reference file tomorrow.


I said; You said;

>I can recreate the problem of misreading the reference
>information every time.  To do this simply create a record
>and add a field from a database file.  If the source code
>has the following for a keyword;
>
>REFFLD(LIBNAME/FILENAME FIELDNAME)
>
>You have a great setup.  Save and exit the source, then
>bring it back up in the designer.  On my installation it
>will show the field as a one character I/O field.  It
>defaults to this because it can't find the referenced file.
>  It interprets the parameters of the REFFLD incorrectly,
>and inserts things in the wrong places.  What it does is
>put *LIBL in the library prompt, FIELDNAME in the file name
>prompt, LIBNAME in the record name prompt, and FILENAME in
>the field name prompt.  It does it every time, and causes
>me to have to manually fix it.  It recognizes it correctly
>before the save and quit, just not when it loads the source
>again.  If you still need source, I would be glad to share
>the DDS for the reference file and the window I am
>designing.
>
>======================>
>When I look up REFFLD in the online DDS manual it shows me something like
>this:
>
>REFFLD([record-format-name/]referenced-field-name
>[{*SRC | [library-name/]database-file-name}])
>
>I would expect the behaviour to be exactly as you describe.
><======================

Jim Essinger
Senior Programmer/Analyst
Student Loan Fund of Idaho
esinger@fmtc.com
208-452-4058