Which way to go?

[dogboss]

Hi,

I'm looking for some implementation advice.....

I have a client who has a 3rd party supplied property database. The client wants this database, through their web site to be searchable by any visitor - at the moment, that's the spec; no online updates to the database at all - purely for look-up purposes.

Here's my quandary: the third party database will be supplied in msaccess format. The 3rd party will, on demand, be able to provide an 'updated' version of the database i.e. the entire database (not just changes since the last 'bulk' download) but with any 'new info' price changes etc.

I know I can access msaccess thru php using odbc drivers/Pear etc but.......support is much greater for php/MySQL AND the current host doesn't support msaccess......

So

implementation-wise, should I convert the access db to MySQL? or, is the effort involved in that too much for not much gain?

Any pointers gratefully accepted.

[bad76]

Hi,
you can get msaccess db and export into a csv file. Then import it in mysql.

Or setup a local server with odbc for access and mysql (myodbc...) and on this you swap from access to mysql (with program like datapump of borland it's quick...).

[Pig]

It would be faster for look ups if you convert it to mysql. However, then you have set up a system to convert it every time.

It would be simpler to use an odbc.