I "inherited" the Access 2003 project. Now they began to modernize us until 2007. I am a low person on the totem pole (and rightly so), so I don’t have access - ha, no pun intended - to Big Mama Oracle db, only dumps that were saved as tables (and built into many queries) in Access.
So, some very simple questions to understand.
From this discussion, I learned that due to the complexity of the reports, I have to think about stored procedures. Ok, I like this idea. This is good programming.
Access 07 supports (apparently) something like stored procedures (right?). However, I read scary things about it, and most of the rest of the department has not yet been updated with '03. If I do my work in '07, their '03 will not know what to do with my beautiful stored procedures, right? FURTHERMORE, if it turns out that '07 is really NOT the right choice for this project (for some reason - who knows, new to this operation), then all the time spent on investments instantly becomes obsolete.
Since Big Mama IS is an Oracle drum, it is obvious that it must be stable. So why don't I just wrap my head around SP in Oracle? It seems that this will lead to the most reliable application for everyone: I was given to understand that I can teach both Access'03 and '07 how to call these Oracle SPs. In addition, my coding will be lower and closer to the source, which contributes to stability and efficiency.
Can I create an Oracle-oriented SP in Access '07 (or '03). I doubt it.
source
share