Re: MSAccess to Web App

RonG <rgafron@xxxxxxxxxxxxx> wrote in
news:01b70a4c-44c3-452d-8aa5-4485466214d7@xxxxxxxxxxxxxxxxxxxxxxxxxxx
m:

[]

Yes, there are plenty of people who don't want their data put on
someone else's server, but given the tremendous growth of Internet
banking, one would have to believe that this is becoming less and
less of a concern.

Online banking is really not in any way analogous to what you're
proposing for your app. Before online banking (either over the
Internet, or with the old dialup clients) the bank owned the data
about your accounts -- you didn't own it at all. You still don't own
the data, just the money.

But banks are regulated in a way that makes your money safe.

There is no corresponding regulation for web hosts in regard to data
safety and security, so you can't use online banking as an analogy
for trustworthiness with data.

Not something to be ignored, but certainly not the
issue it once was.

I agree with the concern you raised about whether the userbase
would be agreeable to moving to a web-based model. It seems to be
almost age-related across the customerbase.

Regards getting crossed off of some lists, I think that that
really varies across industries and demographics. I'm working
with sole proprietorships for the most part. They aren't looking
for a network based application that supports lots of users, that
they can install in their office. These are single users, for the
most part. In that group, you'll have plenty who don't want to
deal with computers any more than they have to, and I think would
be happy with a web app, since they don't have to install
anything. Others like the idea of having more control. Which
group is larger, I don't know.

I believe that a web app may be the best thing for our users, but
there is the reality of support that comes into play. I don't have
a staff of programmers; I have me. If I build to a platform that
requires a lot of support, then that's taking time away from new
development, which is where the income comes from. In a very real
sense, I have to balance the technology needs of the users against
the business needs of my business. I have to build something that
they want, but I also have to build something that I can support.

You also commented about a problem with a web app being that
there's no guarantee that your data actually belongs to you. With
all due respect, I think that that's incorrect. For one thing,
ownership of the data should be clearly stated in the licensing
for the product.

Legally, yes. But in a practical sense, if you don't actually have
the ability to, say, go into a web control panel for the database
and do a data dump any time you like, then you don't really control
it (even if you technically own it).

Personally, I would never lock a business out of their data for
non- payment of services. That is simply unethical. Regardless,
in the big picture, the customer's data belongs to them; I am
simply warehousing it for them as part of the ASP.

And it's not worth much without the app itself, as it's unusable.
This means that a customer who stops paying gets locked out of the
app but doesn't lose access to their data (by some mechanism?). Not
that this is of much use to them without the interface for
retrieving and editing that data.

[]

In the near term, that will probably
mean supporting both a PC-based as well as a web-based
application. There are things I can do with a PC-based app that
would be difficult to do in a web app, and vice versa. I suppose
the best solution would be a development platform that would
support a single codebase that could be rolled out as either a web
application or as a platform- dependent app for Windows, Mac, etc.
During my research, I did come across a platform that said it
could do this, called ActiveState Tcl. I couldn't get my hands
wrapped around whether it could actually do what it said with a
good level of quality, but that remains a possibility as well.

Anyone who is promising a single codebase for distribution on the
desktop and the web is a charlatan. The interfaces have to be
completely different, which means the desktop app will really just
be a web app running locally.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.

Relevant Pages

  • Re: AD Authentication From Windows Forms
    ... This is a WinForms app, not a web app. ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: AD Authentication From Windows Forms
    ... This is a WinForms app, not a web app. ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Repeatable hard crash with 2.6.0.test[123]
    ... One application will reliably cause the system to crash when it exits ... This app worked fine and exited correctly ... the few changes needed to get the 2.kernels running. ... # ACPI Support ...
    (Linux-Kernel)
  • Re: Application Flow / security issues
    ... You won't need a special service account. ... If the use case of the app is basically to have a user log in and then loop ... I just checked with corp. and if I want to do delegation I have to ask ... - You are using integrated windows auth in your web app ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Schannel and Session Renegotiation
    ... Schannel does not support the server sending app ... We are discussing the option of providing support for the client blowing off ...
    (microsoft.public.platformsdk.security)