Code designer bugs - are there fixes for these problems?

Greetings,

I am trying to design an AS/400 screen in Code Designer,
and am running into problems. On the file level I have the
keyword that points to an externally described file that is
my reference field. I then try to add a field from that
file. Code Designer does not default to that file, but
asks for which file I would like to get my field. If I add
without a prompt, it adds a field from a file that is
totaly unrelated file and a library I don't have in my
library list.

When I do a save, the little window comes up to say that it
is saving, but then hangs there. It does not ever advance,
so it is hard to tell if the source actually got saved.

When I finally get a referenced field on my display, and
have it saved (I look at the source to make sure the
changes happened, and got saved with SEU or Code editor) i
then bring the souce back up in the designer, and it loses
all track of those referenced fields. The keyword for the
reference points specifily to the lib/file field-name, but
when looking in properties for the field, the library says
*libl, the field name is in the file prompt, the library
name is in the record prompt, and the file name is in the
field prompt. To make it work right I have to fix all but
the lib prompt, and then it uses the file keyword for the
database reference to point to the file and record.

It crashes quite frequently, and I lose source when it
does.

Are there fixes available for the designer? Is this thing
ever going to work properly so I don't have to spend time
fixing the code? I don't want to go back to SDA, but it
seems that the designer is not quite ready for prime time.
 (are we using alpha or beta code?????)

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

I am on Win 2000 Pro Service pack 2 with most of the fixes
downloaded from the internet.

On the developer I am at the following levels:
IBM WebSphere Development Tools for iSeries
Version: V5R1M0
Pathname: C:\WDT400\
Installation Date: 12/10/2001

The following list gives the service and configuration
levels of each installed product component:

Component: CODE/400
Service Level: 4

Component: Distributed Debugger
Version: 9
Pathname: C:\IBMDEBUG
Service Level: 1

Component: VisualAge for Java for Windows
[Installed]

Component: Webfacing
Service Level: 4

Component: Base
Service Level: 4

Component: SDK
Service Level: 4

Component: ET400
[Not Installed]

Component: VisualAge for RPG
Service Level: 4

Component: WebSphere Studio
Service Level: 4

Component: NetQuestion
Program Folder: C:\IMNNQ_2K