All done in MS Access and now they want a web front end and SQL backend

[EGBOK]

I have spent nearly a year creating a database to track project progress. The database has gone live and everybody is impressed with it. Never contemplated that this would cause so many attention. Now the formal request came through that I should change the front end to a web gui and obvioulsy the backend to SQL.

Can you tell me what would be the best software to use to start creating the front end again. I figure that I would have to do queries, reports and forms from scratch?? A LOT of work. I am well versed with Frontpage but there is no way that I can duplicate what I have done in Access with Frontpage.

The users are currently accessing the database via a Sharepoint Portal that actually just links to the database in Access so the user still needs Access (which is a pretty standard application). Should I consider changing the database into an exe??

Any suggestions will be welcomed BEFORE I go off and tackle this beast!

[NeoPa]

How about starting by making it clear to these ....s that "converting" to a web front-end is not converting at all, but a complete rewrite, in an unfamiliar language and environment to boot.
It may seem obvious to you, but oftentimes managers (etc) ask for the impossible as they're simply too ignorant of the issues to realise how something that fits so easily into their understanding can actually be a little more complicated when it comes to doing the actual work.

[HiTechCoach]

Should I consider changing the database into an exe??

You can not compile an Acess MDB to an EXE. You will always need a version of Access installed to run the database. There is a runtime version that can be installed without having to purchase Access for each machne. In 2007 there is a free runtime version of Access. In earlier versions you have to by the Developer version to get the runtime license to distribute it.

If you want to create a web front end, you will need to use a server side scripting language like ASP (FrontPage can be used) or ASP.NET/VB.NET.

To do it web based, it will take at least 2 to 5 time longer to create. So you are looking at several years since it took you almost a year in Access.

If you really think you want o do completely rewrite everything web based with an SQL server back end then before you start you should:

Assuming that you will be working full time (50 to 80 hours a week) as a developer then you should expect to:

1) Spend at least 6 months learning SQL server.
2) Convert your current Access database front end to to use an SQL server back end. This way if you do build a web based front end, you can use both Access and the Web based front end at the same time with the same back end.

3) Spend at least 6-12 months learning ASP.NET and VB/NET
4) Start writing your web based front end.

I have spent nearly a year creating a database to track project progress. The database has gone live and everybody is impressed with it. Never contemplated that this would cause so many attention. Now the formal request came through that I should change the front end to a web gui and obvioulsy the backend to SQL.

Can you tell me what would be the best software to use to start creating the front end again. I figure that I would have to do queries, reports and forms from scratch?? A LOT of work. I am well versed with Frontpage but there is no way that I can duplicate what I have done in Access with Frontpage.

The users are currently accessing the database via a Sharepoint Portal that actually just links to the database in Access so the user still needs Access (which is a pretty standard application). Should I consider changing the database into an exe??

Any suggestions will be welcomed BEFORE I go off and tackle this beast!

[ineuw]

Any suggestions will be welcomed BEFORE I go off and tackle this beast!

I just noticed your post. Have you made any decisions yet? If you have, I would be curious to know, since I have faced a similar issue and studied it at length.

ineuw