RE: Re: [OT] PHP & Access help required

["Alex Monaghan" <ha@xxxxxxxxxxxxxx>]

In simple terms, you need a web page on server A to respond to formatted
web
requests from server B, it will in effect be an Access query proxy.

Server B instead of making an ODBC call, it would post the formatted query
string to http://serverA/AccessProxy.aspx
which would return the result of
your query.

As you're running ASP.NET & PHP, then you should have no problem in
taking a
query string and result set and converting to XML to pass the data between
servers.

Simple :)

Naturally you'd put a security layer round it, but this just a very simple
overview.

If you Google, then you can probably find example code.

> -----Original Message-----
> From: Keith Finnett [mailto:keith@xxxxxxx]
> Sent: Tuesday, March 01, 2005 8:30 PM
> To: ukha_d@xxxxxxx
> Subject: [ukha_d] Re: [OT] PHP & Access help required
>
>
>
> It has to be an Access database, as it's an established website on
> an ASP.NET server that I don't want to change.
>
> I don't think scheduled jobs are an option, unless I introduce
> server C (!) and make it run a job to extract the data from server A
> and upload it to server B, but i'd rather not use a third box.
>
> I was approaching the conclusion of using some kind of interface but
> didn't really know where to start. I'll take a look at RPC.
>
> Any other pointers helpful!!!
>
> Keith
>
>
> --- In ukha_d@xxxxxxx, Stuart Grimshaw
> <stuart.grimshaw@g...> wrote:
> > On Tue, 01 Mar 2005 07:35:49 -0000, Keith Finnett
<keith@f...>
> wrote:
> > If it, positively, absolutely HAS to be an access database, and
> > copying it over on a scheduled basis isn't an option, then you
> could
> > implement some kind of xml-rpc interface (or lightweight
> alternative)
> > between the two and have server b make requests to the rpc
> interface
> > of server a which then accesses the db and returns the results.
> >
> > --
> > -S
> > http://www.makepovertyhistory.org/
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>