Hi Victor,

yes, that's about our limit without an SSD. We also use Crystal Reports, and so that eats up some horsepower at the end of the month/quarter/year when lots of reports are being run.

And in fact we are moving in that direction. Unless Lianja were to implode, which seems very unlikely given that the backing company, Recital, has been around for 24 years, we will be moving into the "run on everything, everywhere" world.

Hank

>>Hi Victor,
>>
>>the issue with terminal services (I'm involved with two Enterprise apps that offer hosted deployment on ica and rdp respecively) is TCO.
>>
>>One real server (a couple of quad core Xeons) running an efficient web app can probably serve 1,000 users. With a hard-hitting large VFP app it is much fewer. With an SSD for temp files, you might get 100 on a 64-bit server. Not that VFP is 64 bit, but Win2K8 will put the OS above 4 gig (except for a small sliver), which leaves more space below. In the end, it comes down to TCO.
>
>I've had a VFP app running on a server that about 30 users connect to via terminal services to run a VFP application - it's been running for 5 or so years with no problems. I was kind of against doing it that way when I started the project, but they already had the TS licenses so it was easy for them to justify doing it that way.
>
>>Anyway, the thread wasn't about running VFP for web applications: it was about using VFP code to do the programming for a fully modern application able to run on desktop, desktop browser, mobile browser, and native client (the latter with VFP code running on the native client OS, either iOS or Android). I can see why you might have been misled: the attempts to discredit this approach have strayed from the point of discussion.
>
>ha - well like I said I hadn't been following the thread. Anyway so the idea is to use VFP for a desktop, browser, mobile browser, and different O.S's. I'm still a little confused as to why anyone would even want to try to do that...VFP isn't made for all that - why not just use a development tool that's made for such things to begin with?
>Remember VFP 3.0?? That one you could compile for Windows or Mac - which was pretty neat. I was very disappointed then 5.0 came out and discovered they'd removed that feature.
>
>
>>What I know for sure is that my boss would love to move off ica. It works great (and has for the 10 years we've been using it for this). And he'll be able to charge less and make more when we're able to switch over. That kind of thing always makes him happy. :)
>>
>>Hank
>>
>>>>Lets give a user the ability to pick a customer and then show him all his records in nice sortable grids. Let him edit current records and add new ones. Lets publish to a convenient webserver.
>>>>
>>>>How much effort is there to do that in VFP9 SP2?
>>>>
>>>>How much do you think there is in ASP.NET?
>>>
>>>I haven't been following this thread so forgive me for kinda jumping in here....
>>>
>>>One thing I've never quite understood is why anyone would want to write a web app with VFP to begin with - seeing how it's not intended to be used that way. The only thing that makes sense to me would be to write a VFP app and then use Terminal Services so people can log into a server's desktop and use it like that - and considering the costs of the TS licences in most cases this isn't really too bright of an idea either. Now if you you want a website people can go to and such to pick customers, enter data in sortable grids etc etc - it seems like there are about a zillion other tools intended for that purpose and doing it with VFP makes to sense too me. Perhaps I'm missing something???