Re^3: Absolute simplest way to keep a database variable persistent?

To apply a nomenclature that may help understand clwolfe's idea consider the Perl application as a server and your VBA code as a client. The overall process is a little like using OLE to allow one application (your VBA code) to connect to another application (the Perl code).

In fact it may be that using OLE is exactly the solution you are looking for. It is not a 'free' option however. ActiveState provide tools for doing the heavy lifting as part of their pro package. See OLE automation server and Creating a COM/OLE server for some discussion of this option.

Perl reduces RSI - it saves typing

Comment on Re^3: Absolute simplest way to keep a database variable persistent?

Replies are listed 'Best First'.
Re^4: Absolute simplest way to keep a database variable persistent? by natestraight (Novice) on Oct 10, 2008 at 12:11 UTC
OLE / COM does sound like exactly what I need, but anything non-free (barring paltry sums... say less than $20) really is out of the picture for now. This is primarily a pet project, not a necessity, and I can't think of a time when I would need to use Perl again.	[reply]