Re: Interfacing from Apache to Access
On Tue, 11 Jul 2000 15:10:25 -0600 (MDT), rise wrote: >On Tue, 11 Jul 2000, Mike Miller wrote: >> Not good for heavy use, but for the 3-4 times a month >> it gets used in production, it works perfectly okay. > >There is one significant issue with using DBD::Proxy / DBI::ProxyServer on >Windows: lack of fork. If you're going to be using it you probably want to >either use 5.6 (problem mostly solved) or start several proxies on >differenct ports. Check the PlRPC & Net::Daemon docs for informations >about forking. This is mainly annoying because only one connection can use >the single process proxy at once. Otherwise we've seen no problems with >using it as production method to slurp data from an Access DB into a >RRDBMS (Real Relational Database Management System tm). > Thanks for the info. I've never hit this because the only process that uses the proxy is initiate from a cron job (on a unix box) that runs every hour looking for updates in the access db (which gets updated 3-4 times a month, if that ). It is also the only task that ever uses the proxy, so of course I'd never see it. For me the entire entire thing was a hack, but what the hey, it works ... Brgds, Mike.
Re: Interfacing from Apache to Access
On Tue, 11 Jul 2000, Mike Miller wrote: > Not good for heavy use, but for the 3-4 times a month > it gets used in production, it works perfectly okay. There is one significant issue with using DBD::Proxy / DBI::ProxyServer on Windows: lack of fork. If you're going to be using it you probably want to either use 5.6 (problem mostly solved) or start several proxies on differenct ports. Check the PlRPC & Net::Daemon docs for informations about forking. This is mainly annoying because only one connection can use the single process proxy at once. Otherwise we've seen no problems with using it as production method to slurp data from an Access DB into a RRDBMS (Real Relational Database Management System tm). Jonathan Conway Senior DBA ipoPros.com
Re: Interfacing from Apache to Access
On Tue, 11 Jul 2000 14:52:58 +0100 (BST), David Mitchell wrote: >> From: Eric Strovink <[EMAIL PROTECTED]> wrote: >> Write a simple socket interface to connect Apache Perl to your existing >Windoze Perl script (which you'll hack to set up as a simple server). Invent >your own protocol. Locking issues will come >> up, but you can manage this yourself with a little creativity. There are >pretty good examples of how to do simple socket things with Perl, in the Perl >books. > >This has already been done! See DBD::Proxy. > >This allows you to run a little perl Program on the machine with the Access >DB which acts as a proxy DB server, then the client uses >DBD::Proxy (as opposed to DBD::Oracle or whatever) to access the >database. >Never tried it myself, but it sounds cool! > I use it regularly, and it works fine ... Not good for heavy use, but for the 3-4 times a month it gets used in production, it works perfectly okay. Brgds, Mike.
Re: Interfacing from Apache to Access
DBD::Proxy does work the way you describe it. I've used it with succes to address MSSQL DBs. So far, with Access I met a few difficulties with memos (Access' BLOBs), but maybe I didn't find the way to do it. Fabrice David Mitchell wrote: > > > From: Eric Strovink <[EMAIL PROTECTED]> wrote: > > Write a simple socket interface to connect Apache Perl to your existing > Windoze Perl script (which you'll hack to set up as a simple server). Invent > your own protocol. Locking issues will come > > up, but you can manage this yourself with a little creativity. There are > pretty good examples of how to do simple socket things with Perl, in the Perl > books. > > This has already been done! See DBD::Proxy. > > This allows you to run a little perl Program on the machine with the Access > DB which acts as a proxy DB server, then the client uses > DBD::Proxy (as opposed to DBD::Oracle or whatever) to access the > database. > Never tried it myself, but it sounds cool! > > * Dave Mitchell, Operations Manager, > * Fretwell-Downing Facilities Ltd, UK. [EMAIL PROTECTED] > * Tel: +44 114 281 6113.The usual disclaimers > * > * Standards (n). Battle insignia or tribal totems
Re: Interfacing from Apache to Access
> From: Eric Strovink <[EMAIL PROTECTED]> wrote: > Write a simple socket interface to connect Apache Perl to your existing Windoze Perl script (which you'll hack to set up as a simple server). Invent your own protocol. Locking issues will come > up, but you can manage this yourself with a little creativity. There are pretty good examples of how to do simple socket things with Perl, in the Perl books. This has already been done! See DBD::Proxy. This allows you to run a little perl Program on the machine with the Access DB which acts as a proxy DB server, then the client uses DBD::Proxy (as opposed to DBD::Oracle or whatever) to access the database. Never tried it myself, but it sounds cool! * Dave Mitchell, Operations Manager, * Fretwell-Downing Facilities Ltd, UK. [EMAIL PROTECTED] * Tel: +44 114 281 6113.The usual disclaimers * * Standards (n). Battle insignia or tribal totems
Re: Interfacing from Apache to Access
Lorenzo Gordon wrote: > Hello, > > I am a software developer for The London School of Hygiene & Tropical Medicine, UK. > My query is the following: I have been able to successfully run a Perl script from >MS-DOS that would pull out the necessary info. from an Access database I wrote last >year (Access 97). > > The problem is that in order to get the script to talk to the web pages i am >currently designing, the script must run on the School's network, which is a Unix >Solaris machine running Apache. > Both the School's Web Administrator have been struggling (and so far failing) to >find an ODBC-like driver that will enable Unix to talk to Access via my Perl script. > > The implications of not been able to create some connection between these various >componenets are massive. > > Any solutions/pointers/advice anyone might have would be greatly appreciated. I >can't believe I'm the first person to have come across this problem! > > Please respond either to [EMAIL PROTECTED] . > > TIA, > > Lorenzo Gordon. You should probably think about converting your Access database to SQL Server. Access is not a good choice for a production server, nor will it ever be, since Micros~1 wants to keep selling SQL Server. Look at some of the old threads about interfacing to SQL Server for more information. Having said this, I'll assume that there are powerful forces beyond your control that make it impossible to shitcan Access. So, here's something that will work, as long as your traffic load is light. Write a simple socket interface to connect Apache Perl to your existing Windoze Perl script (which you'll hack to set up as a simple server). Invent your own protocol. Locking issues will come up, but you can manage this yourself with a little creativity. There are pretty good examples of how to do simple socket things with Perl, in the Perl books. HTH.
Re: Interfacing from Apache to Access
Look! It's a big orange burning circle in the sky... Run away, RUN AWAY If you have any say in things DO NOT implement a web interface to an access DB. Migrate the access DB to a true SQL server that won't suffer the many problems that access does. Geoffrey Young wrote: > > look into DBI and DBD::ODBC on CPAN > (http://www.perl.com/CPAN-local/modules/by-module/) > > from the DBI mailing list, I gather lots of folks use DBD::ODBC for > perl-MSAccess connectivity... > > HTH > > --Geoff > > > -Original Message- > > From: Lorenzo Gordon [mailto:[EMAIL PROTECTED]] > > Sent: Monday, July 10, 2000 9:45 AM > > To: modperl > > Subject: Interfacing from Apache to Access > > > > > > Hello, > > > > I am a software developer for The London School of Hygiene & > > Tropical Medicine, UK. > > My query is the following: I have been able to successfully > > run a Perl script from MS-DOS that would pull out the > > necessary info. from an Access database I wrote last year (Access 97). > > > > The problem is that in order to get the script to talk to the > > web pages i am currently designing, the script must run on > > the School's network, which is a Unix Solaris machine running Apache. > > Both the School's Web Administrator have been struggling (and > > so far failing) to find an ODBC-like driver that will enable > > Unix to talk to Access via my Perl script. > > > > The implications of not been able to create some connection > > between these various componenets are massive. > > > > Any solutions/pointers/advice anyone might have would be > > greatly appreciated. I can't believe I'm the first person to > > have come across this problem! > > > > > > Please respond either to [EMAIL PROTECTED] . > > > > TIA, > > > > Lorenzo Gordon. > > -- __ Mr. Erich L. Markert [EMAIL PROTECTED] Computer Learning Center TEL (914)422-4328 Pace University 1 Martine Ave White Plains, New York 10606-1932 Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer
Re: Interfacing from Apache to Access
This question is better suited for the dbi-users mailing list. See http://www.symbolstone.org/technology/perl/DBI/ I've successfully used DBD::ODBC under Solaris to access Access via Openlink's middleware. http://www.openlinksw.com/ John [EMAIL PROTECTED]
RE: Interfacing from Apache to Access
look into DBI and DBD::ODBC on CPAN (http://www.perl.com/CPAN-local/modules/by-module/) from the DBI mailing list, I gather lots of folks use DBD::ODBC for perl-MSAccess connectivity... HTH --Geoff > -Original Message- > From: Lorenzo Gordon [mailto:[EMAIL PROTECTED]] > Sent: Monday, July 10, 2000 9:45 AM > To: modperl > Subject: Interfacing from Apache to Access > > > Hello, > > I am a software developer for The London School of Hygiene & > Tropical Medicine, UK. > My query is the following: I have been able to successfully > run a Perl script from MS-DOS that would pull out the > necessary info. from an Access database I wrote last year (Access 97). > > The problem is that in order to get the script to talk to the > web pages i am currently designing, the script must run on > the School's network, which is a Unix Solaris machine running Apache. > Both the School's Web Administrator have been struggling (and > so far failing) to find an ODBC-like driver that will enable > Unix to talk to Access via my Perl script. > > The implications of not been able to create some connection > between these various componenets are massive. > > Any solutions/pointers/advice anyone might have would be > greatly appreciated. I can't believe I'm the first person to > have come across this problem! > > > Please respond either to [EMAIL PROTECTED] . > > TIA, > > Lorenzo Gordon. >
