Access v Browser Based applications.

[Pauldohert]

Can anyone offer any reasons to go for Access and SQL Server applications as opposed to browser based.

The current climate seems to be that if its browser based it all good and non web enabled is all bad, regardless almost of any functionality the two may offer.

Is there a list of reasons that can be put to support non browser based applications - or should I just give up and move to only brower based solutions.

Hope that provokes some good responses on an access site!!!

Paul

 

[pono1]

Paul,

Every project is different -- so it's difficult to generalize...

One thing about Access -- once you know your way around, you can build a pretty decent DB application fairly quickly. A not-so uncommon scenario: A company needs a DB that will be used in-house by one, maybe two, possibly three people. The interface needs to be functional but not necessarily pretty since there will be a captured audience. Access version xyz is already installed on the office computer(s). Getting the app up and running quickly is top priority. Access is a fine solution here...

Another scenario: A company wants to build an app that will be used by many people across a wide area network (different offices in different cities). They don't want to worry about installing the client (the front-end) -- and they suspect the user base will grow steadily over time. A web-based app would probably be a better solution here since a browser will most probably already be installed on company PCs...

Different tools for different tasks... Always, too, cost will play a part in things -- as well as the skillset of the people available to do the job.

Regards,
Tim

 

[Pat Hartman]

The current climate seems to be that if its browser based it all good and non web enabled is all bad, regardless almost of any functionality the two may offer.

That just goes to prove the point that stupid people shouldn't breed.

As Pono has pointed out, good practice is to choose the correct tool for the job. I personally dislike web based applications. I find them slow and clunky. I don't like the flat looking forms and the constant scrolling.

The major advantage that web apps have over client/server applications is their ease of deliverablity. Client/server applications need to be "installed" and that means that modifications also need to be "installed" and this can be very complicated. In fact the "installation" issue was the driving force behind web development. Access has the additional problem of requiring either the retail or runtime version of Access to be installed on the target machine. The other advantage (slight) that web apps have is that they are more suitable to a wide-ranging user community where you don't have any control over the client's hardware or software. But this really falls into the "know your requirements" bucket and would certainly influence the decision in choosing the correct tool.

 

[JACKSON]

Great discussion point !

I agree with everything said, it really depends on the scope of your project. Since they have already talked about the upsides of web based, Here are ome positives on an Access "server based" vs "Browser based" systems :

- You don't have to worry about your cable going down
- Speed is generally better with a local server based application for local users (by server I simply mean BE / FE model).
- Cost can sometimes be higher upfront with a server based model, but ASP systems generally carry significanly higher ongoing monthly maintenance costs for the client.
- Data is stored on-site, which depending on your application, can be important to the client.

As example, we just converted a client from an ASP application to our access application hosted locally. They can't believe the speed differential, and downtime is pretty much non-existant, which was not the case with their previous system.

Anyway, just me 2 cents.

 

[Pauldohert]

Keep these reasons coming!!!! Thanks guys.

How about things like reports and moving mass amounts of data into and out of databases?