CN115630086B - Method for converting Access application into Web application program - Google Patents
Method for converting Access application into Web application program Download PDFInfo
- Publication number
- CN115630086B CN115630086B CN202211654298.9A CN202211654298A CN115630086B CN 115630086 B CN115630086 B CN 115630086B CN 202211654298 A CN202211654298 A CN 202211654298A CN 115630086 B CN115630086 B CN 115630086B
- Authority
- CN
- China
- Prior art keywords
- module
- low
- data
- code platform
- access
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/248—Presentation of query results
Abstract
The invention provides a method for converting Access application into Web application program, comprising the following steps: the low code platform imports Access information of the Access application and converts the Access information into a data table; the low-code platform generates a Web application program, and searches the required data in the data table according to a request sent when the Web browser runs the Web application program; and displaying the required data by the Web browser. According to the invention, any Access application is imported into the low-code platform, and each Access application can realize application conversion without being re-manufactured on the low-code platform, so that time and labor are saved, and the development cost is saved; in addition, the invention also converts the Access SQL statement into the SqLite SQL statement on the basis of realizing the conversion of the Access application native function into the low-code platform function, thereby facilitating the user to inquire data through a Web browser.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a method for converting Access application into Web application program.
Background
The Access database is used in a standard Web browser, and a developer can design the Access database with reasonable structure and convenient use according to the application requirements of users by using the Access. In order to query data in the Access database, a developer needs to create relationships in a plurality of tables, however, the process of creating the relationships needs the developer to read the service logic and the database design of the original Access application for each database. Has the defects of high development cost, time consumption and labor consumption.
The Web browser is a client program which is used most frequently, and how to enable different Web browsers to conveniently display files in different Access application programs in batches and enable users to interact with the files, so that the development cost is reduced, and the problem which is solved by practitioners is solved.
In view of the above, it is necessary to develop a method for converting Access application into Web application to reduce development cost.
Disclosure of Invention
The invention provides a method for converting Access applications into Web application programs, which can lead any Access application into a low-code platform, realize application conversion without re-manufacturing each Access application on the low-code platform, save time and labor and save development cost; in addition, the invention also converts the Access SQL statement into the SqLite SQL statement on the basis of realizing the conversion of the Access application native function into the low-code platform function, thereby facilitating the user to inquire data through a Web browser.
The technical scheme for realizing the purpose of the invention is as follows:
a method for converting an Access application into a Web application program comprises the following steps:
the low code platform imports Access information of the Access application and converts the Access information into a data table;
the low-code platform generates a Web application program, and searches the required data in the data table according to a request sent when the Web browser runs the Web application program;
and displaying the required data by the Web browser.
In a possible implementation manner, the importing, by the low-code platform, access information of an Access application, and converting the Access information into a data table includes:
the low code platform establishes connection with the Access application through the connection character string and opens the connection;
reading a table, data, a view and a page of the Access application by the low-code platform;
the low code platform converts tables, data, views and pages into metadata;
the low code platform processes the metadata into a data table.
In a possible implementation manner, the reading, by the low-code platform, of the table, the data, the view, and the page in the Access application includes:
analyzing the Access application by the third-party database;
the third-party database establishes the Access application into a table data module, a query module and a form module;
the low code platform reads tables, data, views, and pages from the table data module, query module, and form module of the third party database.
In a possible implementation manner, the third-party database establishes the Access application as a table data module, a query module and a form module, and includes:
the table data module comprises a table structure and table data;
the query module screens and queries the table data through an SQL command and rearranges query results;
the form module is used for collecting data and storing the collected data in the form data module;
the low code platform reads tables, data, views and pages from a table data module, a query module and a form module of a third-party database, and comprises the following steps:
the low-code platform reads the table structure and the table attribute from a table data module of a third-party database, and acquires table information and data information from the table structure and the table attribute;
the low-code platform reads the view structure and the view attribute from a query module of a third-party database, and obtains view information from the view structure and the view attribute;
and the low-code platform reads the interface result and the interface attribute from the form module of the third-party database and acquires page information from the interface structure and the interface attribute.
In one possible implementation, the low code platform converts tables, data, views, and pages into metadata, including:
the low code platform converts the table information, data information, view information and page information into metadata.
The low-code platform acquires the table structure and the table attribute, the view structure and the view attribute and the interface attribute of the table data from the third-party database, and determines the table information, the data information, the view information and the page information according to the table data attribute, the view attribute and the interface attribute.
In one possible implementation, the low-code platform generates a Web application, including:
the low code platform converts the Table structure and the Table attributes of the Table module of the Access application into a Table module;
the low code platform generates a view module by using the structure and the attribute of a Query module in the Access application;
the method comprises the steps that a low-code platform generates a page module according to the structure and the attribute of a Form module in an Access application;
the table module, the view module and the page module run into a Web application program in a Web browser;
the Web application program of the low-code platform is embedded into an SQLite database, the SQLite database stores input data collected by a page module, and the SQLite database calls metadata from a server of the low-code platform.
In a possible implementation manner, the searching for the required data in the data table according to a request sent when the Web browser runs the Web application includes:
the method comprises the steps that a low-code platform receives a request sent by a Web application program;
the low code platform expresses the request as a SqLite SQL query statement;
and the low-code platform directly searches the required data by using the SqLite SQL query statement, or converts the SqLite SQL query statement into the Access SQL query statement and searches the required data.
In one possible implementation, the low-code platform selects to directly use the SqLite SQL query statement to search for the required data, and includes:
the required data is directly searched in the SQLite database by the SqLite SQL query statement, and the low-code platform provides the required data for the Web browser.
Converting the SqLite SQL query statement into an Access SQL query statement and searching the required data, wherein the method comprises the following steps:
if the Access data volume of the Access application is large, the SqLite SQL query statement can directly find first required data in a server of a low-code platform, the low-code platform provides the first required data for the Web browser, and simultaneously converts the SqLite SQL query statement into the Access SQL query statement, the low-code platform finds second required data in the server of the Access application, and the low-code platform continues to provide the second required data for the Web browser;
if the Access data volume of the Access application is general, the low code platform converts the SqLite SQL query statement into the Access SQL query statement, searches the required data in a server of the Access application and stores the required data in an SQLite database, and provides the required data for the Web browser;
if the Access data volume of the Access application is small, the SQLite database stores all the Access data volume, the SqLite SQL query statement directly searches for required data in the SQLite database, and the low-code platform provides the required data for the Web browser.
In one possible implementation manner, the generating, by the low-code platform, a Web application, and searching for the required data in the data table according to a request sent when the Web browser runs the Web application includes:
the low code platform converts the Table structure and the Table attributes of the Table module of the Access application into a Table module;
embedding a Web application program of a low-code platform into an SQLite database;
the data in the low code platform from the Access database calling table module is stored in an SQLite database, and the SQLite database also stores input data collected by a Web application program;
the method comprises the steps that a low-code platform receives a request sent by a Web application program;
the low code platform converts the request into a SqLite SQL query statement;
the low code platform uses the SqLite SQL query statement to look up the required data in the SQLite database.
Compared with the prior art, the invention has the beneficial effects that:
1. the invention converts the Table module (data Table), query module (Query) and Form module (interface Form) of the Access application into the Table, view and page corresponding to the low-code platform through the third-party database, thereby realizing the migration of the Web application program. And then any Access application can be led into the low-code platform, and each Access application can realize application program conversion without re-making an application program on the low-code platform, so that time and labor are saved, and development cost is saved.
2. On the basis of realizing the conversion of the native function of the Access application into the application function of the low-code platform, the Query module of the Access application is converted into the view, the application program of the low-code platform runs the view in a Web browser, and the low-code platform generates SqLite SQL Query statements after acquiring Query contents from an edit box of the view, so that the required data can be conveniently searched, and the Query difficulty is reduced.
3. The invention converts the Access SQL statement into the SqLite SQL statement, and is convenient for a user to inquire data in the SqLite database through a Web browser.
Drawings
FIG. 1 is a flowchart of a method for converting an Access application into a Web application program according to the present invention.
Detailed Description
The present invention is described in detail with reference to the embodiments shown in the drawings, but it should be understood that these embodiments are not intended to limit the present invention, and those skilled in the art should understand that functional, methodological, or structural equivalents or substitutions made by these embodiments are within the scope of the present invention.
Referring to fig. 1, an embodiment of the present invention provides a method for converting an Access application into a Web application, including:
the low code platform imports Access information of the Access application and converts the Access information into a data table;
the low-code platform generates a Web application program, and searches required data in a data table according to a request sent when a Web browser runs the Web application program;
the Web browser displays the required data.
The conversion of the Access application into the Web application program is mainly a conversion process, and the Access application generally consists of three parts, namely a data Table, a Query (equal to views in other databases), and an interface Form. Therefore, the process of converting an Access application into a web application program comprises the following main steps: reading an Access application file; converting Table, query and Form in the Access application file; generating a table, a view and a page corresponding to the low-code platform; the web application is generated by a low code platform. The low code platform of embodiments of the present invention is preferably a type grid.
In the above scheme, the importing, by the low code platform, access information of the Access application, and converting the Access information into the data table includes:
the low code platform establishes connection with the Access application through the connection character string and opens the connection;
reading a table, data, a view and a page of the Access application by the low-code platform;
the low code platform converts tables, data, views and pages into metadata;
the low code platform processes the metadata into a data table.
It should be noted that, when the low-code platform according to the embodiment of the present invention reads an Access application, a connection is first established, then a table and data are read, a view is read, and finally an interface is read. When the connection is constructed, an OleDB connection character string is constructed according to an Access file path (path) input by a user (the connection character string is used for connecting databases, and the connection character string is used for connecting various databases).
In the above scheme, the reading, by the low-code platform, of the table, data, view, and page in the Access application includes:
analyzing the Access application by the third-party database;
the third-party database establishes the Access application into a table data module, a query module and a form module;
the low code platform reads tables, data, views, and pages from the table data module, query module, and form module of the third party database.
In practical application, it is preferable that reading the Access application file requires a third-party database, the third-party database is used for analyzing the Access application, and the Access can be established into a corresponding object through the third-party database, so as to read the attribute in the Access. And acquiring specific structures and attributes of relevant contents such as tables, queries and interfaces required in the conversion process. Preferably, the third-party database is microsoft, office, inter, access, and system, data is a system class library provided by a NET Framework.
It should be noted that, the reading of the table, data, view, and page in the Access application by the low code platform in the embodiment of the present invention specifically includes: establishing connection with an Access file through a connection character string, simultaneously opening the connection, and acquiring all tables by using an OceDB method GetOceDbSchemableable, wherein the method returns a result set, traverses the result set, constructs a T ABLE object with a NAME of Table1 and a Table of a self-defined class, and is used for storing relevant attributes of each Table, acquiring the Table NAME from a T ABLE _ NAME column of each row and setting the Table NAME value on the Table attribute of Table1; using a GetSchema and GetOleDBSCHEMA method of an OleDB to query a table structure corresponding to a table name, returning a result set containing all columns and attributes of the columns, traversing each row of the result set, and constructing a Column object with the name of Column1 and Column as a self-definition class for storing the relevant attributes of each Column; each row represents a column owned in the table and its attributes. Respectively acquiring whether a COLUMN IS self-added, COLUMN name, COLUMN type and unique according to IsAutoIncrement, columName, dataT type, isUnique, IS _ NULLABLE and COLUMN _ DEFULT. And is arranged on the column1 object; column1 is added into the Columns attribute of the table1 object, the main key corresponding to the table name is inquired by using the GetOleDBSCchemaT method of OleDB, and the method returns a result set containing all the main key Columns; traversing each row of the result set, adding a primary key column to Primarykeys of the table1 object according to the table name, and constructing SQL (structured query language) according to the table name and all column names on the table1, such as Select C1 and C2 fromstable 1; using an OLEDB to execute SQL to obtain a result set, wherein the result set is a data table, and adding all data into Rows attributes of the table1 object by traversing the result set; adding table1 into a set with T able as a type for facilitating subsequent use; adding table1 to a set of type T able for subsequent use (after the structure of each table is obtained, the foreign key is obtained later); using the method of OleDB GetOleDBSCHEMA to inquire all the foreign keys, and the returned result set contains all the foreign key information (the foreign keys are the names of the primary key table, the primary key column, the foreign key table and the foreign key column, and also contains the constraint rule); traversing the result set, constructing an external key object, and adding a main key list, a main key column, an external key list, an external key column name, an updating rule and a deleting rule to the external key attribute of table1 (the updating rule is divided into two cascades and a node); and closing the connection and ending the access to the database.
In the above scheme, the third-party database establishes the Access application as a table data module, a query module and a form module, and includes:
the table data module comprises a table structure and table data;
the query module screens and queries the table data through an SQL command and rearranges query results;
the form module is used for collecting data and storing the collected data in the form data module;
the low code platform reads tables, data, views and pages from a table data module, a query module and a form module of a third party database, and comprises:
the low-code platform reads the table structure and the table attribute from a table data module of a third-party database, and acquires table information and data information from the table structure and the table attribute;
the low-code platform reads the view structure and the view attribute from a query module of a third-party database, and obtains view information from the view structure and the view attribute;
and the low-code platform reads the interface result and the interface attribute from the form module of the third-party database and acquires page information from the interface structure and the interface attribute.
It should be noted that the reading table, data, view, and page in the embodiment of the present invention specifically include: an object of a View set is constructed, the name is View List, the View set is used for storing each read View, all views are read and added into the set object (in an Access database, the query mainly comprises two types, the first type is a View, the View is to carry out screening query and rearrange honest results by correlating the data in the existing tables through SQL commands.)
The read view process may be: opening a connection through a connection string; using a GetOleDbSchematable method of an OleDB to acquire information of all views, and returning a result set by the method; traversing a result set; constructing a view object for storing read information, and assuming the name of the view object to be view1; acquiring a value of T ABLE _ NAME from an object of each line as a view NAME, and storing the value on an attribute of view1; obtaining a structure of the View by using an OleDBGetSchema method according to the name, and returning a result set by the method; acquiring an SQL statement of VIEW from the VIEW _ DEFINIT ION attribute by traversing a result set; analyzing by a self-defined configured ANT LR syntax tree, translating the original Access SQL into SQL of a database used by a low-code platform, storing the final SQL on the attribute of view1, adding the view1 into a view List, and continuously traversing a result set until the traversal is finished.
The page reading process of the embodiment of the invention can be as follows: creating an access.application object with the name app1 (access.application is part of microsoft. Office. Inter. Access of the aforementioned third-party library); opening an Access file of a specified path by using an app1 method OpenCurrentDatabase; acquiring all interfaces (Form) in the Access application through app 1; traversing the result set, acquiring the name of the page, and then executing an opening command on each interface by using the openForm of the app 1; and traversing all the interfaces again (traversing the interfaces-converting the interfaces) until the traversal is finished, and closing the database through the CloseCurrentDatabase of the app 1.
Traversing the interface-converting the interface comprises the following steps: acquiring the type of the Form according to the input Form object; constructing a PageExporter object (the PageExporter is an object of metadata after a page is read, wherein the PageExporter object contains a page name, layout details and no converted page element (control)); form types are judged (Form types are two, others or Datasheet).
If the Form type is other, a PageRuler object is constructed, named Ruler1. The PageRuler is a self-defining class and is used for storing the layout of a page, wherein the layout comprises the number of rows and columns, the width and the height of each row and column are respectively, and the positions of all controls of a header, a detail and a footer, the uppermost left corner and the lowermost right corner are respectively obtained; traversing the positions of all the controls, taking out two x attributes of each control, adding the two x attributes into an x set, and setting the name as an xList; sorting the xList to enable the values in the xList to be sorted from small to large; according to the value of xList, columns are added to rower 1 and the width of each column is calculated. Traversing all the controls, taking out two y attributes of each control, adding the two y attributes into an x set, and sequencing yLists by setting the name as yList, so that the values in the yList are sequenced from small to large; according to the value of yList, add rows to ruler1 and calculate the width of each row. Traversing all controls, and regenerating the position information of the controls according to the rows and columns in the rubber 1; after the conversion is completed, all controls are added to the PageExporter object. Judging the form type again, if the form type is a continuous form, acquiring detail again and uploading to a repeat page; acquiring all controls on a repeater, creating a ruler object, and constructing a layout (line, row width and column width) ("the constructing process of the repeater page is similar to that of a common page, except that a header and a footer are not included, and only a detail part is included); storing the page layout result of the repeat and all controls on the T biplate attribute of the PageExporter; acquiring the column number of a data table on a SpiltForm page; initializing a table for the pageExporter object, wherein the number of columns is the same as that of the original page, and the number of rows is 40; traversing all converted controls, and searching for a picture type control; extracting picture attributes including names, picture data, position information (row and column), and width and height of the picture on the picture control; and returning the picture object and adding the picture object to the pageExporter attribute. If the form type is Splitform, acquiring the column number of a data table on a Spiltform page; initializing a table for the pageExporter object, wherein the number of columns is the same as that of the original page, and the number of rows is determined to be 20; traversing all converted controls, and searching for a picture type control; extracting picture attributes including names, picture data, position information (row and column), and width and height of the picture on the picture control; the picture object is returned and added to the pageExporter attribute.
If the Form type is Datasheet, acquiring the column number of a data table on the Spiltform page; initializing a table for the pageExporter object, wherein the number of columns is the same as that of the original page, and the number of rows is 40; traversing all converted controls, and searching for a picture type control; extracting picture attributes including names, picture data, position information (row and column), and width and height of the picture on the picture control; and returning the picture object and adding the picture object to the pageExporter attribute.
In the above solution, the low code platform converts tables, data, views and pages into metadata, including:
the low code platform translates table information, data information, view information, and page information into metadata.
The low-code platform acquires the table structure and the table attribute, the view structure and the view attribute and the interface attribute of the table data from the third-party database, and determines the table information, the data information, the view information and the page information according to the table data attribute, the view attribute and the interface attribute.
In the above solution, the low-code platform generates a Web application, including:
the low code platform converts the Table structure and the Table attributes of the Table module of the Access application into a Table module;
the low code platform generates a view module by using the structure and the attribute of a Query module in the Access application;
the method comprises the steps that a low-code platform generates a page module according to the structure and the attribute of a Form module in an Access application;
the table module, the view module and the page module run into a Web application program in a Web browser;
the Web application program of the low-code platform is embedded into an SQLite database, the SQLite database stores input data collected by a page module, and the SQLite database calls metadata from a server of the low-code platform.
In the above solution, searching for the required data in the data table according to a request sent when the Web browser runs the Web application includes:
a low-code platform receives a request sent by a Web application program;
expressing the request as an SqLite SQL query statement by the low-code platform;
and the low-code platform directly searches the required data by using the SqLite SQL query statement, or converts the SqLite SQL query statement into the Access SQL query statement and searches the required data.
In the above scheme, the low code platform selects to directly use the SqLite SQL query statement to search for the required data, and includes:
the required data is directly searched in the SQLite database by the SqLite SQL query statement, and the low-code platform provides the required data for the Web browser.
Converting the SqLite SQL query statement into an Access SQL query statement and searching the required data, wherein the method comprises the following steps:
if the Access data volume of the Access application is large, the SqLite SQL query statement can directly find first required data in a server of a low-code platform, the low-code platform provides the first required data for the Web browser, and simultaneously converts the SqLite SQL query statement into the Access SQL query statement, the low-code platform finds second required data in the server of the Access application, and the low-code platform continues to provide the second required data for the Web browser;
if the Access data volume of the Access application is general, the low code platform converts the SqLite SQL query statement into the Access SQL query statement, searches the required data in a server of the Access application and stores the required data in an SQLite database, and provides the required data for the Web browser;
if the Access data volume of the Access application is small, the SQLite database stores all the Access data volume, the SqLite SQL query statement directly searches for required data in the SQLite database, and the low-code platform provides the required data for the Web browser.
In the above scheme, the generating, by the low-code platform, the Web application, and searching for the required data in the data table according to the request sent when the Web browser runs the Web application includes:
the low code platform converts the Table structure and the Table attributes of the Table module of the Access application into a Table module;
embedding a Web application program of a low-code platform into an SQLite database;
the data in the low code platform from the Access database calling table module is stored in an SQLite database, and the SQLite database also stores input data collected by a Web application program;
the method comprises the steps that a low-code platform receives a request sent by a Web application program;
the low code platform converts the request into a SqLite SQL query statement;
the low code platform uses the SqLite SQL query statement to search the required data in the SQLite database.
The embodiment of the invention converts a Table module (data Table), a Query module (Query) and a Form module (interface Form) of the Access application into a Table, a view and a page corresponding to a low-code platform through a third-party database, thereby realizing the migration of Web application programs. And then any Access application can be led into the low-code platform, and each Access application can realize application program conversion without re-making an application program on the low-code platform, so that time and labor are saved, and development cost is saved.
The embodiment of the invention converts the Query module of the Access application into the view on the basis of converting the native function of the Access application into the application function of the low-code platform, the application program of the low-code platform runs the view in a Web browser, and the low-code platform generates the SqLite SQL Query statement after acquiring the Query content from the edit box of the view, so that the required data can be conveniently searched, and the Query difficulty is reduced.
The embodiment of the invention converts the Access SQL statement into the SqLite SQL statement, thereby facilitating the user to inquire data in the SqLite database through a Web browser.
The embodiment of the invention mainly solves the defect that each Access must be manually made again in the prior art. The Access application can be directly converted into an engineering file of a low-code development platform, and the subsequent web application development is automatically completed through the low-code development platform. Compared with the prior art, the development cost and the migration cost can be effectively reduced.
The above-listed detailed description is only a specific description of a possible embodiment of the present invention, and they are not intended to limit the scope of the present invention, and equivalent embodiments or modifications made without departing from the technical spirit of the present invention should be included in the scope of the present invention.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Furthermore, it should be understood that although the present description refers to embodiments, not every embodiment may contain only a single embodiment, and such description is for clarity only, and those skilled in the art should integrate the description, and the embodiments may be combined as appropriate to form other embodiments understood by those skilled in the art.
Claims (3)
1. A method for converting an Access application into a Web application program is characterized by comprising the following steps:
the low code platform imports Access information of the Access application and converts the Access information into a data table;
the low-code platform generates a Web application program, and searches required data in the data table according to a request sent when a Web browser runs the Web application program;
the Web browser displays the required data;
the low code platform imports Access information of the Access application and converts the Access information into a data table, and the method comprises the following steps:
the low code platform establishes connection with the Access application through the connection character string and opens the connection;
reading a Table module, a Query module and a Form module in the Access application by a low-code platform;
the low code platform converts the Table module, the Query module and the Form module into metadata;
the low-code platform processes the metadata into a data table;
the low code platform reads a Table module, a Query module and a Form module in the Access application, and comprises the following components:
analyzing the Access application by the third-party database;
the third-party database establishes the Access application into a table data module, a query module and a form module;
the low-code platform reads tables, data, views and pages from a table data module, a query module and a form module of a third-party database;
the low code platform generates a Web application comprising:
the low code platform converts the Table structure and the Table attribute of the Table module of the Access application into a Table module;
the low code platform generates a view module by using the structure and the attribute of a Query module in the Access application;
the method comprises the steps that a low-code platform generates a page module according to the structure and the attribute of a Form module in an Access application;
the table module, the view module and the page module run into a Web application program in a Web browser;
the Web application program of the low-code platform is embedded into an SQLite database, the SQLite database stores input data collected by a page module, and the SQLite database calls metadata from a server of the low-code platform;
the searching for the required data in the data table according to the request sent when the Web browser runs the Web application program includes:
the method comprises the steps that a low-code platform receives a request sent by a Web application program;
the low code platform expresses the request as a SqLite SQL query statement;
and the low-code platform directly searches the required data by using the SqLite SQL query statement, or converts the SqLite SQL query statement into the Access SQL query statement and searches the required data.
2. The method of claim 1, wherein the third-party database builds the Access application into a table data module, a query module, and a form module, and comprises:
the table data module comprises a table structure and table data;
the query module screens and queries the table data through an SQL command and rearranges query results;
the form module is used for collecting data and storing the collected data in the form data module;
the low code platform reads tables, data, views and pages from a table data module, a query module and a form module of a third-party database, and comprises:
the low-code platform reads the table structure and the table attribute from a table data module of a third-party database, and acquires table information and data information from the table structure and the table attribute;
the low-code platform reads the view structure and the view attribute from a query module of a third-party database, and obtains view information from the view structure and the view attribute;
and the low-code platform reads the interface result and the interface attribute from the form module of the third-party database and acquires page information from the interface structure and the interface attribute.
3. The method of claim 1, wherein the low-code platform generates a Web application, and searches the data table for the desired data according to a request sent by a Web browser when the Web application is run, and the method comprises:
the low code platform converts the Table structure and the Table attribute of the Table module of the Access application into a Table module;
embedding a Web application program of a low-code platform into an SQLite database;
the data in the Access database calling table module is stored in an SQLite database by the low code platform, and the SQLite database also stores input data acquired by a Web application program;
a low-code platform receives a request sent by a Web application program;
the low code platform converts the request into an SqLite SQL query statement;
the low code platform uses the SqLite SQL query statement to look up the required data in the SQLite database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211654298.9A CN115630086B (en) | 2022-12-22 | 2022-12-22 | Method for converting Access application into Web application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211654298.9A CN115630086B (en) | 2022-12-22 | 2022-12-22 | Method for converting Access application into Web application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115630086A CN115630086A (en) | 2023-01-20 |
| CN115630086B true CN115630086B (en) | 2023-03-10 |
Family
ID=84910630
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211654298.9A Active CN115630086B (en) | 2022-12-22 | 2022-12-22 | Method for converting Access application into Web application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115630086B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103309806A (en) * | 2013-05-03 | 2013-09-18 | 上海证券交易所 | Device and method for fast developing and testing |
| CN114115952A (en) * | 2021-11-30 | 2022-03-01 | 苏州瀚码智能技术有限公司 | Method and device for automatically upgrading packaged low-code application |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2354862B (en) * | 2000-01-11 | 2002-04-03 | Ecora Com Corp | Method and system for automatic documentation of configurable systems |
| US8549472B1 (en) * | 2007-06-12 | 2013-10-01 | Fair Isaac Corporation | System and method for web design |
| CN106776343A (en) * | 2017-01-13 | 2017-05-31 | 中国科学院软件研究所 | A kind of web application automated test tool and method |
| CN110989983B (en) * | 2019-11-28 | 2022-11-29 | 深圳航天智慧城市系统技术研究院有限公司 | Zero-coding application software rapid construction system |
| CN114510478A (en) * | 2021-12-31 | 2022-05-17 | 福建亿能达信息技术股份有限公司 | General data entry method, device, equipment and medium based on data model |
-
2022
- 2022-12-22 CN CN202211654298.9A patent/CN115630086B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103309806A (en) * | 2013-05-03 | 2013-09-18 | 上海证券交易所 | Device and method for fast developing and testing |
| CN114115952A (en) * | 2021-11-30 | 2022-03-01 | 苏州瀚码智能技术有限公司 | Method and device for automatically upgrading packaged low-code application |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115630086A (en) | 2023-01-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109344223B (en) | Building information model management system and method based on cloud computing technology | |
| CN106202207B (en) | HBase-ORM-based indexing and retrieval system | |
| CN107491561B (en) | Ontology-based urban traffic heterogeneous data integration system and method | |
| CN107515887B (en) | Interactive query method suitable for various big data management systems | |
| CN106598612B (en) | Operation method and system for data table in database | |
| CA2388515C (en) | System for managing rdbm fragmentations | |
| US20160224594A1 (en) | Schema Definition Tool | |
| EP2365447A1 (en) | Data integration system | |
| US20060271885A1 (en) | Automatic database entry and data format modification | |
| CN111813798B (en) | Mapping method, device, equipment and storage medium based on R2RML standard | |
| CA3029638C (en) | Chemical substructure search query building and execution | |
| US20170193036A1 (en) | Framework for joining datasets | |
| CN101493825A (en) | GIS middleware collocation and management method | |
| Varga et al. | QB2OLAP: enabling OLAP on statistical linked open data | |
| CN102779186B (en) | Whole process modeling method of unstructured data management | |
| CN115202626A (en) | Low-code front-end development method supporting multi-technology stack components | |
| CN114443656A (en) | Customizable automated data model analysis tool and use method thereof | |
| CN113297251A (en) | Multi-source data retrieval method, device, equipment and storage medium | |
| CN115630086B (en) | Method for converting Access application into Web application program | |
| JP3914081B2 (en) | Access authority setting method and structured document management system | |
| CN115080011B (en) | Code generation method and system based on abstract syntax tree | |
| CN111125216A (en) | Method and device for importing data into Phoenix | |
| CN111008011A (en) | System builder for power platform application development | |
| CN113722337B (en) | Service data determination method, device, equipment and storage medium | |
| CN113221528B (en) | Automatic generation and execution method of clinical data quality evaluation rule based on openEHR model |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |