Portable cross platform database accessing method and system

• US 8,504,919 B2
• Filed: 08/14/2008
• Issued: 08/06/2013
• Est. Priority Date: 10/16/2002
• Status: Active Grant

• Current Assignee: Mozapps Limited
• Original Assignee: Mozapps Limited
• Inventors: Savage, Shaun
• Primary Examiner(s): Nguyen, Cao Kevin
• Application Number:
  US12/228,593
• Publication Number:
  US 20090013173A1
• Time in Patent Office: 1,818 Days
• Field of Search: 715853-855, 715740-748, 715/734, 715751-765, 715/728, 709/201, 709/209
• US Class Current: 715/734
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application

Abstract

A user manages a database or other application through a remote graphical user interface on a server device through a client device. A cross platform database translation module resides on the client device. The client device may also store cross platform authentication, configuration, and report generating modules for validating a user id and presenting database results in a desirable format. The modules on the client device request applications from a server device, may request validation from an authorization server, may configure embedded devices, and may query a database. The database may reside on a server, on the client device, or on another device.

Claims

1. A non-transitory computer-readable medium device that stores an executable program for accessing a database through a graphical user interface, comprising:

a first component object model module for validating a user, the first component object model module including sub modules, each of the sub modules handling a unique security protocol;

a second component object model module for handling an application from and loading an application from an external device and querying and processing results from querying a database; and

application and widget information for constructing a graphical user interface (GUI), wherein the widget information comprises widgets, widget definitions, and widget processing code, the widget processing code describing actions between the widget and a binary component object model resident on the client device; and

wherein the first and second component object model modules reside on a client device.

2. The non-transitory computer-readable medium of claim 1, wherein the external device is an applications server.

3. The non-transitory computer-readable medium of claim 1, wherein the database is external or internal to the client device.

4. The non-transitory computer-readable medium of claim 3, wherein the component object module is binary and is cross platform.

5. The non-transitory computer-readable medium of claim 4, wherein the first component object model module communicates with an authentication server.

6. The non-transitory computer-readable medium of claim 5, wherein the client device constructs an application from widgets supplied by the applications server.

7. The non-transitory computer-readable medium of claim 6, further comprising a third component object model module for accessing a native database.

8. The non-transitory computer-readable medium of claim 6, the second component object model module including one or more sub modules for accessing native databases.

9. The non-transitory computer-readable medium of claim 6, further comprising a third component object model module for handling a security protocol.

10. The non-transitory computer-readable medium of claim 6, further comprising a fourth component object model module for viewing configuration and status information of an embedded device or remote device.

11. A method of remote graphical user interface processing of data, comprising the steps of:

a client device requesting an application from an external device;

the client device receiving the application and widget information from the external device to construct a graphical user interface (GUI), wherein the widget information comprises widgets, widget definitions, and widget processing code, the widget processing code describing actions between the widget and a binary component object model resident on the client device;

the client device using the widgets and the widget processing code to assemble a GUI;

the client device communicating with the external device using the application through the constructed GUI; and

displaying the application on the client device through a GUI using newly received widget information.

12. The method of claim 11, further comprising the step of processing data using a Javascript database class and the component object model module, wherein the displaying of the application is through a GUI that represents an assembly of widgets through a Javascript database class interface.

13. The method of claim 12, wherein the component object model module is a cross platform component object model module.

14. The method of claim 13, wherein the step of communicating with the external device includes the steps of querying a database, receiving database results, and processing the database results.

15. The method of claim 14, wherein the step of querying a database is accomplished through a structured query language.

16. The method of claim 14, wherein the database is a relational database that is secured through an encrypted index.

17. The method of claim 14, wherein the database is a relational database and each entry of the database has at least one encrypted index.

18. The method of claim 17, wherein the at least one encrypted index is stored in a table.

19. The method of claim 11, wherein the widget processing code received to assemble a GUI is extensible mark up language (XML) code.

20. A method for configuring embedded devices on a network using the method of claim 11, further comprising the steps of:

requesting a configurations application by a client device;

displaying the configurations application on the client device based on widget information;

requesting status and/or configuration information from an embedded device through the configurations application;

displaying the status and/or configuration information from the embedding device on the client device; and

updating the configuration information on the embedded device through the client device.

21. The method of claim 20, further comprising the step of displaying the updated configuration of the embedded device.

22. The method of claim 21, wherein requesting, displaying, and updating of the configuration information for the embedded device is performed through a component object model module on the client device.

23. A method for securing a relational database using the method of claim 11, further comprising the steps of:

accessing a record from a relational database;

generating an unencrypted index for a first field of the record;

storing the unencrypted index in a table;

generating an encrypted index through an encryption algorithm for a second field of the record;

storing the encrypted index in the table; and

using a master key and one of the group consisting of the encrypted index and the unencrypted index to obtain the other of the group consisting of the encrypted index and the unencrypted index.

24. The method of claim 23, wherein the secured relational database is accessed by a remote GUI databasing method.

25. The method of claim 24, wherein the remote GUI databasing method uses a widget based GUI for databasing from a client device.

26. The method of claim 25, wherein databasing functions are performed through one or more cross platform component object model modules resident on the client device.

27. A method for providing a character based user interface to a character based, legacy device using the method of claim 11, further comprising the steps of:

entering a keystroke on a client device;

transmitting the keystroke to a display server; and

equating the keystroke with a page update event or a new page event.

28. The method of claim 27, further comprising, for a page update event, updating the page on the display server and transmitting the page to the client device.

29. The method of claim 28, further comprising, for a new page event, forwarding the new page event information from the display server to a web server.

30. The method of claim 29, further comprising, for a new page event, generating an HTML page on the web server and transmitting the HTML page to the display server.

31. The method of claim 30, further comprising, for a new page event, translating the HTML page to a character based page and sending the character based page to the client device for display.