Could this lead to problems with the array reference?

I don't see any reason that should lead to any problems.

There are other approaches (apart from Win32::API) that you can take - eg XS or Inline::C.
I personally prefer either of those (especially the latter) over Win32::API as I've always found Win32::API difficult to get right - though it's possible that the deficiency is in me, as opposed to Win32::API.

For XS/Inline::C you'll need the header file (which it seems you already have), the dll (which you definitely already have) and a suitable import library (which you might not have).
To create the import library ( let's call it libAID.a), place a copy of AID.dll in the cwd and run:

gendef AID.dll
dlltool --kill-at --input-def AID.def --output-lib libAID.a
[download]

I would then install Inline::C and access the dll functionality using it.
(You'll want to first run perldoc Inline::C-Cookbook for some basic instructions on how to successfully use the module.)

Cheere,
Rob

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.