|
|
Posted by mootmail-googlegroups on 08/10/06 12:32
rcnews@gmail.com wrote:
> It sounds like Microsoft Access is not a favorite among programmers
> here.
It most definitely isn't. I've had to do a somewhat major project with
it, and it was horrible. But while everyone is trying to steer you
away from it and into something more 'practical', allow me to play
devil's advocate...
>
> What I know is that we're currently using PHP (written by
> another technician) to have our website forms filter data into email
> accounts, so that the data can be manually entered later on in Access.
Access sucks. Let's get that out of the way right now. But what it
does do well is allow very easy creation of forms and reports. If you
have an Access system that has been around for years, I would be very
surprised if it didn't already have dozens of forms and reports that
have been added into it over the years. Putting aside the notion of
connecting to Access via PHP for a moment, consider the fact that if
you migrate the data to another database like MySQL, what happens to
all of those forms and reports? You either have to recreate them all
from scratch on the web, or redirect Access to use the remote tables
rather than the internal ones (never done this personally, so I don't
know how easy/reliable it would be). Either way, you're adding more
man-hours to the project which may not be worth the payoff.
When you weigh the options, it may just be more practical right now to
simply connect php to Access to dump the data, and then make a note
somewhere of a nice 'project' that you can do some time down the road
when there is more time/resources available.
Navigation:
[Reply to this message]
|