One thing that’s always bugged me when looking over the sample apps, etc., is how the pages are generally scattered and intermixed. When I create my apps, I try to think everything through first, then I ‘generally’ leave pages 1-200 for typical ‘basic’ screens, like the login/logout, access control, introduction/welcome, etc. My ‘data’ pages I generally don’t start until 300, and I always try to increment succeeding page numbers by at least 2. I also try to ‘group’ my pages in the same set, where the pages in one group (like ‘General info’) would fall in the range of 300 -330, then the next group would begin at 340 or 350. A minor complaint, but especially when trying to follow somebody else’s logic in app design and implementation, it makes it easier trying to see how the pages ‘flow’.

I couldn’t agree more ;)

John.

In short, you can do everything right in APEX, but if your back in PL/SQL sucks, so will your ability to troubleshoot, debug, and support the system.

Just my 2 pence!

:)