designer2000

[michael newport]

does anybody out there use designer2000

in the design editor -> module navigator -> create module -> language

all I find is <null> when I want to create an Oracle Form

any ideas ??

(or should I dump designer and use developer)

[Tony]

mi************@yahoo.com (michael newport) wrote in message news:<63*************************@posting.google.c om>...

does anybody out there use designer2000

in the design editor -> module navigator -> create module -> language

all I find is <null> when I want to create an Oracle Form

any ideas ??

(or should I dump designer and use developer)

I don't know what is causing your problem: you should get a list
including "Developer/2000 Forms" among other things.

However, in response to "or should I dump designer and use developer",
I would say: if all you are doing is building "a form", yes. Using
Designer to generate forms can be a very good idea for a development
project, but it is non-trivial and requires a lot of setting up and
learning the way it works. It doesn't sound like you are ready for it
yet!

[michael newport]

indeed Designer does seem like a separate career !

scenario
--------
learn it and use it once to create a project
then a year or 2 later, you need to make changes to said project
should you go back to the ERD ?
realistically not as you also have to try and remember how to use the
software,
if you are new to the organisation how can you tell if the ERD you see
actually spawned the forms and the code that the users are using.

[Tony]

mi************@yahoo.com (michael newport) wrote in message news:<63*************************@posting.google.c om>...

indeed Designer does seem like a separate career !

scenario
--------
learn it and use it once to create a project
then a year or 2 later, you need to make changes to said project
should you go back to the ERD ?
realistically not as you also have to try and remember how to use the
software,
if you are new to the organisation how can you tell if the ERD you see
actually spawned the forms and the code that the users are using.

I have worked on projects that used Designer and "100% generation" -
in fact I am on one now. If you are on such a project, you should be
aware of the fact - the Designer repository is where you would do all
your work. If you are supporting a legacy system that was originally
generated from Designer, but all the people who built it have left the
company and there is no guarantee that Designer is up to date, or that
forms have not been hand-crafted after generation, and the project
manager doesn't have a view... well then I guess you must form your
own policy!

[michael newport]

I find that a large drawback, you cannot easily see if the whole thing
is up to date (my other problems aside)

and my policy now is to use developer !