Why no web based quicken?

Sure - if your web server is running on Windows... :-)

Remote Desktop :-\

All kidding aside - no Quicken has not be implemented as a web application (and, IMHO, for good reasons).

Question..... why do you think its a god reason they haven't?

And..... if not Quicken.....are there any other web based financial apps like Quicken that do allow web access?

No need for that (installing Q on a web server) to do what you say you wish to (enter/edit info from any computer). Not so good on the edit part (I would assume, could be not even available), but WebEntry does allow you to remotely enter information via quicken.com so that you can download it later upon return to your local machine.

Well that will work I suppose

But ideally it would be nice to check have a web-able version of Q and enter data straight into it rather than going thru hoops above

Yep, I understand what you say. Could fit for some. Just pointing out that the ability to enter via the web and later retrieve transactions already exists. But like I said in my original post, your thought about being able to *edit* existing transactions wouldn't work, so it's not a complete solution for your requirements.

By the way, "me", check out:

?lid=why_0000000000003414854#howitworks(or if the above wraps. Looks like a new version of Quickbooks does what you want!

Please be aware that when entering expenses through the web on a machine (some kiosk or whatever) with a non-US calendar display (e.g. Day/Month/Year), Quicken will import it *blindly* as the date on your home machine (Month/Day/Year) and of course balk at month 28 :) Ah, just as we had left the Y2k hype behind.

Spyro

Try using Microsoft's Remote Desktop Web Connection Software [1}. It requires IIS 4.0 or later, NT Server 4.0 or newer OS, including IIS

6 on XP Pro.

Before you do this, you should have a VERY COMPETENT understanding of the implications of running IIS 6, ActiveX controls, remote desktop, TCP/IP filtering and access control, and DNS. It helps to familiarize yourself with the configuration and product documentation at MS Technet.

Remote Desktop Web connection will allow you to access as much or as little of a system's desktop as you configure in the terminal services profile for the remotely accessing userid. You may configure a single application to launch at startup and for the session to terminate at the end of the application. Alternatively a userid can have a full interactive logon.

Good Luck. I have not done this, so the above is theory only, but should work. If you proceed, I would be interested to hear if you are successful.

Tom Sweet

[1]

It is like installing a wide-open barn door and putting a sign out that says "Hack me!"

Let someone else be the guinea pig, right? I can certainly understand that with such a risky solution.

>

Add setting up a VPN for remote access to the list of tasks. Even if you do that, Quicken still can only be used by one user at a time, right? Can two people enter transactions into Quicken simutaneously?

It can be done, with much of the risks minimized, with much effort. It is my personal opinion that choice of platform is only one factor in the survivability of a system. Quality of the admin is much more significant. Only the OP can decide if the risks are worth the reward. I certainly would not perform the tasks by accepting the defaults in all prompts. That is why I emphasized the level of understanding and some of the items to consider.

Would you have the OP install a *nix flavor, a Windows emulator, and pipe the resultant display via X-Windows and an SSH tunnel? What about making it accessible in a browser? From any system at all?, Without requiring client software installations?

No. I don't throw people blindly into dangerous configurations. The OP was suitably cautioned. Additionally, I don't have the spare equipment to try it. Otherwise, I might have.

Pointers were given to where one could begin to mitigate those risks. Other resources include configuration guides available at sans.org, and securityfocus.com's Microsoft Focus.

Tom Sweet

The VPN is an excellent point, if it is possible to intall software on the accessing system, e.g. your own mobile laptop accessing your home desktop. If the ability to install software exists, then Andrew DeFaria's suggestion to use plain Remote Desktop is better because it has fewer moving parts.

Alternatively, one could obtain an SSL certificate and secure the web communication that way (https).

Even then the Remote Desktop Web Connect still requires an ActiveX control installation into the accessing browser.

If software cannot be installed, full applications or ActiveX controls, then the other Andrew's suggestion to perform transaction entry via quicken.com including the caveats mentioned by Spyro is the only remaining solution.

No simultaneous editing of a Quicken data file. I've never tried to have two Quicken program windows open with two different data files under one or more userid logins. I don't know if XP PRO maintains a console interactive login session when another id tries via Remote Desktop. All of this would have to be tested.

Tom Sweet

Haven't used it, but they get good writeups - try something like GoToMyPC - to allow you to remote back to your desktop. There are others - check out reviews at PCMag.com or CNet or .... As always - there is a risk with opening up this type of access. Check it out and use at your own risk.

- Ron

I don't think an SSL certificate will secure the underlying communication from the ActiveX control to the Remote Desktop Service, which uses RDP protocol on port 3389. It will make your initial request for the ActiveX control secure, but that's it.

Thank you for the correction.

See also Microsoft's "How Terminal Services Works: Terminal Services"

Tom Sweet

allowing even people running Win 2K non server to be able to remotely access a machine.