Ask for their site licenses....I think they have that model. We haven't asked for that because we sell the application to customers who need 1-7 concurrent users.....the 199 US$ of each license works for them and us. We buy the licenses in bulk for us and then install them when our customers need them, at retail price plus a healthy 100%.

>Hi Victor,
>
>We are checking out a demo for GoGlobal. Because our app is a payroll program and every user logs in on the same dates we will almost need one licence per user so it won't be as inexpensive as if each license supported several users.
>
>Thank you for sharing your experience. Other users have expressed satifaction too.
>
>Alex
>
>>GoGlobal was the answer for my needs......full VFP application on the Internet, pretty fast and without changing a line of code. Very low resource consumption and the price is very good (but not free).
>>
>>>Hi Cetin,
>>>
>>>For the future of VFP I'd like to see Rick Strahl or someone with his skills (are there any of those?) create a way to access VFP apps from the browser in a manner similar to the way that Visual WebGui allows access to WinForm apps from the browser. Specifically, what Visual WebGUI does is to use AJAX to send messages to the server which is running an instance of the application for each user. The server then sends messages back to update the browser. That way state is maintained between calls and WinForm apps can be run either locally or via the web.
>>>
>>>See Rick's blog about it. http://www.west-wind.com/WebLog/posts/180727.aspx
>>>
>>>I think the ability to extend the usefulness of existing VFP apps is awesome, not to mention leveraging the skills of VFP developers.
>>>
>>>What you think of this approach for VFP apps?
>>>
>>>Alex
>>>
>>>
>>>
>>>>>Hi everybody,
>>>>>
>>>>>I haven’t been developing VFP programs for about one year now. We need a database and I want to convince my company to use VFP if this is right of course.
>>>>>
>>>>>Some people in the company say that VFP is not supported by Microsoft any more. They believe that we shouldn’t spend money on something that might be obsolete very soon.
>>>>>
>>>>>I was wondering if someone can give me some leads, so I get a solid idea on this.
>>>>>
>>>>>Thank you,
>>>>>Ali
>>>>
>>>>I wouldn't fear by the support end in year 2015. Though support ends my applications would continue to work (like support for older versions ended but even foxbase applications continue to work). Details are our trade secrets but in summary customers' feedback, surprisingly, is towards that we should continue with VFP mostly (instead of deciding ourselves we ask them).
>>>>
>>>>However, OTOH, if you could spare time to learn new things, the stuff for learning is out there for free. You'd at least feel much more armed when you need it. I for one, while enhancing the existing applications and continue to do new versions with VFP spare time (mostly afterhours) to do parallel versions in other backend and languages (I use SQL server 2005,C# and Devforce if you ask). I reached a fluency level with SQL2005 and C# but still yet I couldn't get nowhere near the VFP version. I always preferred to think it's my own inability to understand and use .Net effectively (IOW I still can't dare to say publicly, when it's data .Net cannot cope with VFP, oh did I just say it. Need to find a flamesuit). Probably .Net would close the gap soon and may even be better on that area too (BTW SQL server is already ahead, keeping that aside I think they didn't plan .Net data classes right from the start. Wow more flamesuits needed).
>>>>
>>>>Cetin