Usually the database objects we use in our Apex applications are owned by a schema different to the schema associated with the Apex workspace. We then grant rights (select,insert,update,delete as required) on the objects in the owner schema to the workspace schema.
This setup caused quite a few issues when using the create page/region/process wizards in V3.2 and V4.0. Most of this has been sorted out in V4.1 but there are still some inconsistencies that mean the wizards sometimes cannot be used.
1. Create calendar page or region. When you select an easy calendar you can select a table from the owner schema but then the wizard fails with a no privilege or table not found error.
2. Create form using a sequence from the owner schema. The create form lets you select a sequence from the owner schema and successfully creates the form. However, the form does not work because the sequence used in the process or tabular form does not reference the owner schema.
3. Create form on procedure. The wizard lets you select a procedure in the owner schema but then fails with a no privileges error even though the workspace schema has execute rights on the procedure.
4. Create form pagination process. The wizard does not give you the option to select the table/view from another schema so cannot be used.
5. Create data maniputlation process. The wizard does not give you the option to select the table/view from another schema so cannot be used.
6. Create data load pages. The wizard lets you select the table from the owner schema and creates the pages successfully, but these pages cannot be used because the column names are not populated for the data/table mapping. Hurrah, fixed in V4.1.1!
Creating synonyms in the workspace schema does not solve the problem so I haven't really found any workaround other than creating objects in the workspace schema.