Reinaldo,
Please excuse but I mend with missing in case of RDP.
Sure I know SQL. I have worked with SQL server for years. And I also tried ADS myself. And I think I also saw your video on the ADS homepage.
I don’t know how big the networks of Tim’s customers base are. I felt that his customers are like mines small companies. Therefore I suggested RDP as a solution for him.
It is now nearly over a year that I made my decision to go with my installations the RDP way and there are still questions I have how to organize best the workflow.
But times are changing and for my business ( up to 5 concurrent users) RDP offers a very good solution.
RDP advances rapidly. And Windows Server 2012 offers much more possibilities.
I post here a part from a paper which encourage me and confirmed my resolution:
You are aware of the limitations of DBFCDX in multi user environment. They are required to provide applications to be used by more clients and also over internet. That is the reason to look for alternatives.
Upto 5/6 users DBFCDX is okay. Actually this limit depends on how data intensive and how large are the data tables.
In my view this should not affect WinHotel because the size of DBFs is small and most importantly you are relying more on remote desktop. Performance penalties are very minimum. DBFCDX should serve the purpose with adequate dependability.
Quick review of other alternatives:
1. ADS. This is costly. Some of our developers are taking ADS partnership and selling ADS along with their application. They get price of application as well as margin from ADS for sale of ADS products.
PROS: Rock solid. No index maintenance is needed. Takes full advantage of both ISAM (for browses) and porting legacy code and at the same time SQL of RDMS with the great power for complex queries. Calculations are done on the server and only summary comes to server reducing network traffic and also highly improves speeds.
Free from the limitations of DBFCDX, importantly size. Better performance with more concurrent users and larger tables.
CONS: Cost
Porting problems from legacy ciode ( few but there are issues)
To take full advantage of SQL we need to recode.
2. SQL/RDMS like MySql or its replacements
PROS: FREE
Rock solid databases and limited or no maintenance like ADS
Good performace with unlimited concurrent connections and with very large tables
Advantage of using SQL for complex queries / jobs
CONS Time taken to port the legacy code
Change from RDD kind of programming
My Opinion:
Converting WinHotel to any other RDBMS is now a very big task. Conversion times will be very high/
Conversion to ADS is less time consuming, but it COSTS more to your clients and the benefits may not worth the effort and price.
As it is DBFCDX appears to be quite adequate for the purpose.
Why is thin client and remote desktop computing getting so much attention these days? What are some of the business factors that have changed within recent years to make these applications desirable?
http://enterprisefeatures.com/2011/04/frequently-asked-thin-computing-questions-faq/Best regards,
Otto