Hi

I think you have made the right choice - once you have the frontend developed you can compile it as well. Using an ADP forces you down a certain path, one which I have always found to create more work and maintenance hassles than it was worth. And you are right about the flexibility of the ACCDB with Oracle - ODBC might not be the fastest connection method but it is relatively simple to work with - but then I have been using ODBC for quite sometime now so I'm biased.

You can still utilise stored procedures in the ACCDB format - you just have to execute them via pass-through queries. A nice way to overcome some of the downsides to the way Access handles data. Passing parameters means you are forced to utilise VBA and querydef objects, but they are not difficult and there are plenty of examples around should you need a prompt. You can always post here if you have specific issues.

Using stored procedures via pass-throughs to handle database inserts/updates etc is a bit more work to build but possibly one of the better ways to use Access as a frontend. You have to weigh that sort of design against the standard Access approaches, but if you are working with a lot of unbound forms, I think the sp track is worth the effort. I'm sure a thread on that topic would draw a variety of opinions 🙂

All the best with your development. I hope I was able to help in some manner.

Regards

Rowan