My company has a lot of standalone access databases (2000). Management decided they could just be "web enabled" so they hired a programmer with that experience. Our problem is that the programmers expertise is all microsoft, meaning he wants to convert the access applications to ASP.net, and our environment is all linux/unix. So I was asked to pursue options for converting the ASP to something that runs on Apache (PHP, Java, etc). My issue is being able to support the application after its' converted twice (once from access to asp then again to something apache supports. Wouldn't the code be a mangled mess by then? I've only found one or two peices of software that claim to go from access directly to java or php. No one has a problem using mysql on the backend so at least we agree on that. Any advice would be appreciated. Thanks in advance!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Options for Converting Access
- Thread starter manshack
- Start date
Is there a problem in importing the data to MySQL (it can work as a back-end for Access)?
There are a few notes here:
There are a few notes here:
- Thread starter
- #3
No problem with MySQL at all. That's just the tables with the data. I'm more worried about the front end part. If all the queries, macros, forms and reports are converted to an ASP.net application how do we then move it to something Apache will run? Bottom line Access has to go because the users are getting thin clients with Suse and the microsoft licenses are not going to be renewed.
I came across this on a search, but have not tried it:
- Status
Similar threads
- Locked
- Question
- Locked
- Question