Access / PHP Server Problem

[Jon Crawford]

Hello all-

I am reworking a website that was in really bad shape before I came along.
But some problems have arisen. My client is currently hosting their own
website on a server in their office building. Their internet connection is
poor and the site becomes unavailable periodically throughout the day. The
plan was for me to provide their web hosting instead. I am developing a
database-driven website created in PHP MySQL. But they are absolutely
attached to MS Access. And I use Unix hosting.

I have never used Access so I'm not sure what all my client needs to keep
Access for but I was wondering if anyone had any solutions to this problem.
They want to continue using Access in their office, but the website needs a
more reliable host. And the website's database needs to be more reliably
hosted as well.

Please Help!

 

[Albert D. Kallal]

Hum, it would be easier if you were using something that worked better with
ms-access, and the rest of the desktops.

However, you can certainly use ms-access with any ODBC enabled database.
I don't know if the UNIX box allows odbc connections to mysql
(but, if it does, then that would be my bets - check the mysql newsgroups).

However, you going to need someone with ms-access database
skills, and preferably someone who has interfaced ms-access
with mysql. So, ms-access can work very well in the
environment you speak of, but this assumes that UNIX web server
is opened to odbc connections (it not clear if they are
going to host the machine, or some ISP...if it is a
isp, then check how odbc connections are allowed,
as often MANY WILL NOT allow open odbc
connections to the wild internet. (most will
allow a ssl connection however).

Further, while ms-access can well work with
mysql, you will need an experienced ms-access developer, especially if those
applications were built by a ms-access developer. On the other hand, if
those applications were NOT built by an experienced developer, but
in house by someone with limited knowledge, then is that/them person/people
going to be able to use MySql to create tables etc? will they have this
experience,
or are they willing to learn?

Will the database system be exposed to those end
users..or this not going to be allowed?

When you read between the lines above, much of your problem is not a
technology solution, but what tools and abilities you put in their hands.

I would have to bet that they use and love ms-access for the very reason
they would not want to hire you!!! In other words, they want independence,
and ms-access allows them to build things without hiring expensive
developers. If you move all of the data to MySql, then can those users
continue to build tables, and reports..and even modify..or add fields to the
existing tables? You better quick check as to why they use ms-access
now..but, it sounds like they use it because it allows them to do their
job..and you might be taking that ability away from them..

So, for success of your project, you will need to define the environment,
and what the users need, and how they accomplish their tasks now. If those
users regular create and use ms-access reports, tables etc, then moving to
MySql will an big disaster unless you give them a system that allows them to
do what they do now (or, offer a better alterative).

This is not a technical problem, but one of you sitting down and gathering
requirements, and figuring out EXACTLY what they are using ms-access for...