The Texas Business Software Suite has been designed and built for the unique environment that wireless applications require. This journey started well over a decade ago in 2001 and has come a very long way. We always knew the problem that business software that was originally designed in a mainframe environment had problems working over multiple site and newer SQL servers designed to work over LANs need to function over high powered broadband networks. Wireless is a new medium and has a whole new set of problems, including cost, durability, security and speed.

The fundamental underlining designed of the Texas Business Software Suite is based around hand written stored procedures, a self describing interface similar to SOAP 2 and an entirely encrypted and compressed communication current based on 256 AES and personally encrypted keys.

In order to ensure a smooth communication between client and server, the Texas Business Software Suite has implemented its own Transmission Control Protocol (TCP) designed around asynchronous messages that also incorporated background file transfers. This protocol has involved many versions to ensure the reliable communications in all circumstances even when users are moving from location to location and the signal temporary drops out.

Operating over insecure wireless networks, the security of the communication needs to be ensured. The Texas Business Software Suite has implement its MTCP with the highest level of encryption commercially available, exploiting the process of personally held encrypted keys that effectually have the strengths of passwords of 128 characters long.

One of the unique situations that distributed wireless databases face is the requirement of being auto recoverable when errors occur. The more and more complex business software becomes, the greater the problems that they face and the database need not only ensure that there is continuity of data, but continuity of service. Users are remote from the server and are not always able to restart the server if a drastic problem occurs, or wait for someone to maintain the database, or wait until the database has recovered from backups and the transaction log run.