_________________________ This article improves the Google Apps Script engineering featured in earlier Bit Vectors articles  here ,  here,  and  here  to add file save and print features to a Google Apps Script application. This article will also discuss the potential of Google Apps Script application sharing. Part one  showed the sample application user experience. Part two   described the application configuration . Part three here explained the application engineering. Part four here  will explore how Google Apps Script application sharing presently works and will explain why this is not yet ready for production, based on the present state of the Google Apps Script product . It will also discuss suggested feature enhancements to the Google Apps Script product that would make application sharing possible. Download the three application  component files from the  GitHub repository . ____________________ I n parts o...

_________________________ This article improves the Google Apps Script engineering featured in earlier Bit Vectors articles  here ,  here,  and  here  to add file save and print features to a Google Apps Script application. This article will also discuss the potential of Google Apps Script application sharing. Part one  showed the sample application user experience. Part two   described the application configuration . Part three here will explain the application engineering. Part four   will explore how Google Apps Script application sharing presently works and will explain why this is not yet ready for production, based on the present state of the Google Apps Script product . It will also discuss suggested feature enhancements to the Google Apps Script product that would make application sharing possible. Download the three application  component files from the  GitHub repository . ____________________ T hree files comprise...

_________________________ This article improves the Google Apps Script engineering featured in earlier Bit Vectors articles  here ,  here,  and  here  to add file save and print features to a Google Apps Script application. This article will also discuss the potential of Google Apps Script application sharing. Part one  showed the sample application user experience. Part two  here  will describe the application configuration. Part three  will explain the application engineering. Part four  will explore how Google Apps Script application sharing presently works and will explain why this is not yet ready for production, based on the present state of the Google Apps Script product . It will also discuss suggested feature enhancements to the Google Apps Script product that would make application sharing possible. Download the three application  component files from the  GitHub repository . ____________________ B efore ...

_________________________ In an earlier article , I showed how to front-end Google BigQuery with a Google Docs Spreadsheet / Google Apps Script application. Later articles generalized the engineering: this article  described a Google Cloud SQL front-end application and  this article  explained how to integrate BigQuery and Cloud SQL to build BigQuery stored procedure functionality. This engineering works well enough, but it has some drawbacks: First, it offers no way to save a result set as a finished file. Second, it offers no way to print a result set. Third, the sample applications rely on a container‑based architecture - in other words, the application script files are bound to a Google Sheets file as components of that file. This article describes a sample Google Apps Script application that front-ends a BigQuery project. However, the application also offers file save and print features. Additionally, while its engineering relies on Google Sheets, it br...

______________________ Part one  described the Google Cloud SQL database the sample application uses for the BigQuery "stored procedure" technique. Part two here  will briefly describe important details about the BigQuery project behind the solution. Part three  has an overview of the Google Apps Script solution engineering. Part four  will explain the JavaScript objects behind the Google Apps Script solution. Download the five Google Apps Script component files and scripts for the MySQL stored procedure and the MySQL user-defined function from the  GitHub repository . ________________ T he solution described in this specific article will use the BigQuery project described in this earlier article . For the solution here, name the BigQuery project      BigQuerySPDemoAppDS and create one table called      zbp11totals in it. Load it with data from  zip file " Complete ZIP Code Tota...

______________________ To analyze large data volumes, Google BigQuery  is a great tool. Through  Google Apps Scripts , we can easily build universal web applications  to front-end BigQuery. The JavaScript engineering behind these web applications certainly works well enough, but a major pain point remains: BigQuery does not handle stored procedures . This article describes a sample Google Apps Script solution that front-ends both BigQuery and Cloud SQL, using Cloud SQL to simulate BigQuery stored procedures. In this approach, a JavaScript function takes a Cloud SQL / MySQL stored procedure name and an array of stored procedure arguments as parameters. The function returns a BigQuery result set in a JavaScript array. Of course, when / if Google provides a BigQuery stored procedure feature, it will have a completely different user / developer experience and completely different engineering. However, this new approach works really well and it makes BigQuery front...

______________________ Part one  described the Google Cloud SQL database the sample application uses for the BigQuery "stored procedure" technique. Part two described important details about the BigQuery project behind the solution. Part three here has an overview of the Google Apps Script solution engineering. Part four will explain the JavaScript objects behind the Google Apps Script solution. Download the five Google Apps Script component files and scripts for the MySQL stored procedure and the MySQL user-defined function from the  GitHub repository . ________________ T he engineering for this solution closely matches the engineering described in the earlier article . Therefore, we'll focus on the differences between the solutions and the innovations in this solution. Each solution must build a BigQuery query string based on web form user picks, send that query string to a BigQuery project, receive the result set, and write the result ...