I'm trying to implement the OCI in Excel VBA with my end goal of using OCIPasswordChange from an Excel form after the user's password has expired; however my progress has been a bit slow and I was wondering if someone else out there had already blazed this trail and/or if I could get some general advice on the following issue:

My System Setup: Win7 64-bit, Oracle Thick Client 11.2.0 32-bit, MS Office 2013 32-bit, both Windows ODBC and SQL*Plus are connecting to the oracle server and working properly.

The following C code snipit I'm trying to bend to VBA came from: http://database.developer-works.com/...nge+call+in+8i
Please Login or Register  to view this content.
Which I've ported to Excel VBA as: (Warning causes Excel to crash!)
Please Login or Register  to view this content.
The "manual" I found online for OCIInitialize is here: http://docs.oracle.com/cd/B10501_01/...re7.htm#556332

The problem I'm getting with the above VBA code is that when I run it Excel crashes, and when I go to the windows event viewer it's giving an "Exception code: 0xc0000005" which is for an access violation. Looking into oracle's "oratypes.h" file gives "#define dvoid void" and "#define ub4 unsigned int".

So did I port the four void functions:
  • (dvoid *)0
  • (dvoid * (*)(dvoid *, size_t)) 0
  • (dvoid * (*)(dvoid *, dvoid *, size_t))0
  • (void (*)(dvoid *, dvoid *)) 0 )

correctly from C, or am I missing something here?

I can't really tell if the access violation is due to OCIInitialize trying to call back into Excel's space or if I've done the Null function pointers wrong.

Any insights would be appriciated, thank you.