Myth: XBase is not a web-enabled technology Reality: The Recital 9 Database Server is a completely web/internet enabled Visual FoxPro compatible Database Server. The client drivers for ODBC, JDBC and .NET all use TCPIP as their network transport mechanism. Additionally, Recital has a native Linux/Unix ODBC driver that works with PHP on these platforms. Myth: XBase has no standard Reality: both Recital and VFP are derived from the original dBase language of the 80's. Both Recital and Visual FoxPro have extended the original dBase language extensively over the last decade. Both Recital and Visual FoxPro are object-oriented with full support for classes and an OOPS programming methodology. Recital's and Visual FoxPro's OOPS implementations are compatible. Recital 9 is Visual FoxPro language and function compatible. Additionally, Recital 9's SQL is compatible with Visual FoxPro 8.0 SQL. If you know Visual FoxPro you already know Recital albeit on a different platform. Myth: XBase does not support SQL for data access Reality: both Recital and Visual FoxPro support full ANSI SQL capabilities, including outer joins. These can be performed on both local and cross-platform server data. Myth: XBase is not client/server Reality: The client-server model needs a minimum of three elements: a user interface (or front end), a data source (or back end), and some form of data access middleware (like ODBC, JDBC or a .NET Data Provider) that connects these two tiers. These components can all reside on the same machine if you desire. With both Recital and VFP you can use the power of Remote Views and the flexibility of SQL Pass-through to build a robust client-server application.
Myth: XBase is an unsupported product Reality: Recital is fully supported round-the-clock by our skilled software support team from locations in the UK, US, and Asia. Visual FoxPro is still a fully supported Microsoft product. The latest shipping version as I write this article is 8.0 and 9.0 is already in beta testing. Myth: XBase does not handle multi-statement transactions Reality: Recital supports nested multi-statement transaction blocks. The following example uses XBase command syntax but SQL commands are also fully supported.
Myth: XBase cannot be used for business-critical applications Reality: Recital and Visual FoxPro are being used extensively in a wide range of mission critical applications including; Banking, Logistics, POS, Defense, and Insurance. Myth: XBase does not support XML Reality: Recital can export and import data in Microsoft ADO XML format. Using this standard XML format, data can be easily interchanged with other applications both Microsoft and non-Microsoft across all platforms. Myth: XBase applications are not scaleable and cannot be tuned for optimal performance Reality: Recital 9 can run on any Windows, Linux, Unix or OpenVMS platform. Recital supports a wide range of commands for tuning its performance, for example; SET ICACHE for index caching, SET DCACHE for database caching, SET PCACHE for procedure/program caching. Additionally, Recital applications are JIT compiled (similar to .NET) and loaded into shared memory segments on Linux and Unix. This results in reduced memory usage and reduced paging activity when large numbers of users are using the same application. Myth: XBase has a 2GB size limit for data files Reality: Recital 9 has Very Large Database Support (VLDB). This allows database tables and other associated files (e.g. memo files ) to be up to 2^63 in size. Myth: XBase is not a .NET enabled language Reality: Recital 9 Visual Developer is a client/server execution architecture that .NET enables XBase applications. Myth: XBase does not support structured error handling Reality: both Recital and Visual FoxPro handle modern structured error handling contructs using the TRY/CATCH/THROW commands.
Conclusion
|
||||||||||||||||