we have a Foxpro Application and need to share data accross the web and read it in to a MySQL DB. After a user has edited it (no problem there) it should be transferred back.
I guess using Foxpro is the real wtf here =)

Anyway, as already stated you cannot use OLE on the linux server side easily, so I suggest that you create some kind of Server/API on the application machine and let your webserver communicated with that, instead of directly to the DB. Then you can use any protocoll you want and you abstract away database specicfic code on your webserver.

You get the idea. The possibilities for implementing this are endless. Chose from plain get/post, soap, xml-rpc, csv, or whatever for transportation and HTTP::Server::Simple, Catalyst, Jifty, etc. for the code. Writing a simple CRUD application with one of the advanced frameworks is a piece of cake. You should be able to set one up within minutes. While I'm at it, I think I should also point you at DBD::Xbase, just in case you didn't already know about it.

update: I forgot to mention, if you for whatever reason still need to use COM and OLE (yes they belong together) have a look at the Perl Dev Kit


holli, /regexed monk/

In reply to Re: COM Objects and the need to know more by holli
in thread COM Objects and the need to know more by moggs

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.