Oops, I was close. I suggest Rainer's site to any techie with a CE device. He's ported some useful stuff to CE: wget, flite, ftp, a command line, perl, apache, tk, stunnel and more. I used stunnel to get an IMAPS connect before the inbox client supported, but IMAPS is now supported in WindowsMobile2003 or whatever they call it now...

I have loaded both Perl56 from Rainer and Perl58 from PerlCE.

Perl56 worked and I was able to grab a file via http. It supports Socket, Win32::OLE, Win32::Com, and Win32::API. You can do GUI stuff with Tk. The website says people have successfully talked to a SQLCE db.

I loaded Perl58 but couldn't get it to run, wasted half a day on it and had to put it aside. Unsure if I corrupted the binary or if there's a dll conflict. I followed the instructions but some areas were vague... There are screenshots, so *somebody* has had it working :-)

The site says it has better compatibility and working PerlIO. It also warns that the prebuilt binaries are heavy on the memory side because they have Unicode and debugging in there. I don't have access to MSVisualC++ so I cannot build my own port.

I'm interested in using Perl for database access using tools like Win32::OLE for a local db with SQLCE or preferably OracleLite, but I'm also interested in exploring other access paths like DBD::Proxy for serverside db or even SOAP if the XML overhead isn't too much. I'm thinking about a daemon the runs constantly so as to avoid the startup penalty, something like POE that could handle requests in a single thread without forking...

---

---

• 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.