Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Oracle Apex

  • 25-03-2015 2:03pm
    #1
    Registered Users, Registered Users 2 Posts: 211 ✭✭


    Has anybody got any experience of developing small apps in Oracle Apex and MSAccess . I have experience with PL/SQL and I have been tasked with building a small application (Money in/ Money out kind of thing). Excel has been mentioned, but based on bitter experience I'm not a fan of using spreadsheets for multi-user small apps. So I'm looking at using either Apex or Access and I'm interested in hearing the opinions of anyone who has used both APEX and Access and what their opinion of Apex for developing small apps is vis-a-vis Access?

    Thanks
    Tagged:


Comments

  • Registered Users, Registered Users 2 Posts: 23,212 ✭✭✭✭Tom Dunne


    Apex makes it easy to develop bad code that is functional and looks pretty. :)

    While I haven't worked on it for at least a year now, I would say it is slightly more cumbersome to develop in compared to access (haven't done that in many years), but once you get your head around the web-based development environment, it's actually relatively straight forward. Oracle pitch it as a department-level (as opposed to enterprise class) replacement for access.

    For what you want, Apex does sound like the tool for the job, especially if there are multiple concurrent users.

    Just one word of caution - watch out for licensing issues. Oracle aint cheap, Apex technically comes with a database you have already purchased (or paid the license for). So just downloading Apex (or a version of the DB with it ready to go) is not actually as straight forward as you might think.


  • Registered Users, Registered Users 2 Posts: 211 ✭✭grouchyman


    Tom Dunne wrote: »
    Apex makes it easy to develop bad code that is functional and looks pretty. :)

    While I haven't worked on it for at least a year now, I would say it is slightly more cumbersome to develop in compared to access (haven't done that in many years), but once you get your head around the web-based development environment, it's actually relatively straight forward. Oracle pitch it as a department-level (as opposed to enterprise class) replacement for access.

    For what you want, Apex does sound like the tool for the job, especially if there are multiple concurrent users.

    Just one word of caution - watch out for licensing issues. Oracle aint cheap, Apex technically comes with a database you have already purchased (or paid the license for). So just downloading Apex (or a version of the DB with it ready to go) is not actually as straight forward as you might think.

    Thanks for the reply Tom. The DB licensing side of things is ok and is why apex is being considered. I don't have a tight deadline on delivering anything (some time before December I was told) so I might give it a go and see how I get on, I can alway go back to the spreadsheet or access if needs be.


  • Registered Users, Registered Users 2 Posts: 9,560 ✭✭✭DublinWriter


    I heard that Oracle don't recommend Apex for anything mission-critical?


  • Registered Users, Registered Users 2 Posts: 23,212 ✭✭✭✭Tom Dunne


    I heard that Oracle don't recommend Apex for anything mission-critical?

    Yes, that's correct. Though the cynic in me can't help but feel that is more to do with marketing rather than technology.

    As I said above, it's pitched at department-level web apps - relatively low (<100) number of users and non-mission critical.


Advertisement