(Question)Migrate this to phprunner

Hi,
I'm afraid we can't access your Access db on Google. Maybe you just upload some screenshots here?
Chris

Here are screens of one record in 5 views:

Thanks.

Looks feasable to me. Might be some more work to do but that depends on the backend how the data is handled between all those dialogs.
You might want to download the demo and just give it a try.
Chris

Should be possible. PHPRunner supports both tabbed sections and subforms (edit master and details together).
Just in case check 'How to build advanced webforms' tutorial at http://xlinesoft.com/phprunner/php-database.htm

I have converted a few Access projects and I'd expect that you'll be able to pretty much use the backend database as is or with just minor changes. However the frontend will need to be redesigned with consideration of browser based HTML and server design. At first you'll be able to get raw access to your data tables and put in some relationships and basic validations. That you'll be able to do in a few hours if you haven't done it already, including setting up a user access control system. In a jam that could be rolled out to support a range of remote clients overnight. Very cool.
What will take some time is trying to emulate the forms you have. While you will be able to recreate the same functionality, the way it works may end up being quite different (no matter which way you go). With a bit of work you'll be able to come up with something quite useable. But its not going to be the same. Access lets you do things like scroll up and down seamlessly through 100,000 records with no visible lag, to spagetti code whatever you want, use Activex controls.
Access is a rich client environment, as is Flash and a variety of other proprietary solutions. Browsers on the other hand are very limited, but everyone has one. While browser-based technology has been essentially stagnant for the past decade, the good news is a major upgrade is starting to happen with HTML5/CSS3 and I believe this is the right direction to go. Flash and proprietary solutions for a rich client experience will no longer be required.
I guess the question to start with is why are you converting from Access to a web-based browser server design? If you need to be able to support a variety of new users over the internet/intranet using different platforms without requiring any software/plugin installation or maintenance or client licenses, then that is a very good reason. Then the work on the re-implementation of the front-end will be justified. And the rollout can be incremental.

For just transferring the db to MySQL, there are lots of tools for that, but one that I have used successfully is by a company called SoftGalaxy, http://www.softgalaxy.net/access-mysql/index.html -I have no affiliation of any kind with them. I'd be interested in any other recommendations.
Best,

Ken

I've used DBConvert, license is not too expensive, and it works. Access lets you have field names with special characters like "?". You'll need to rename these. You can do this manually before conversion, or the conversion tool may give an option of converting special characters for you. You'll also need to decide what to do with the foreign keys, and how to handle default values. Both of which is better handled within PHPR. Personally I remove all default values and foreign keys from the DB and put them into PHPR. Check that all the indices you need are there. I suggest that after conversion, go through all the tables and check out what you got is right. Some text fields maybe better as varchar(255) rather than as medium or longtext, also check the creation of blobs is whatcha want. Some conversion programs may struggle with very large or unusual binary fields, or PHPR may not know how to handle them.