Dimensional Data

The BlobStreams sample shows you how to use the BLOB streaming techniques of FireDAC. To this end, this sample implements both the external streaming and the internal streaming. Location You can find the BlobStreams sample project at: Start | Programs | Embarcadero RAD Studio Sydney | Samples and then navigate to: Object PascalDatabaseFireDACSamplesComp LayerTFDQueryBlobStreams Subversion Repository: You can find Delphi code samples in GitHub Repositories. Search by name into the samples repositories according to your RAD Studio version. How to Use the Sample Navigate to the location given above and open BlobStreams.dproj. Press F9 or choose Run > Run. Files File in Delphi Contains BlobStreams.dprojBlobStreams.dpr The project itself. fBlobStr.pasfBlobStr.fmx The main form. Implementation Before running the sample, the main components are configured at design time using the Object Inspector as follows: Two TFDQuery objects named qSelect and qInsert. These components are used to implement the datasets capable of executing SQL queries. The following setup is needed: Configure the Connection property of both objects to specify the FireDAC connection object that is used to connect to a DBMS. In both cases it is set to FDConnection1. Set the SQL property for both objects. It specifies the SQL statement to execute for the query. The SQL property of qSelect is set to select * from {id FDQA_Blob}. The SQL property of qSelect is set to insert into {id FDQA_Blob} (blobdata) values (:blobdata). Configure the qInsert.Param[0]: The Name property is se to BLOBDATA The DataType property is set to one of the BLOB data types. In this sample ftBlob. The ParamType property is set to ptInput. It means that the stream will be read and written to a database BLOB value. The StreamMode property is set to smOpenRead. This is the default value. It means that the stream is used to read the database BLOB value. A TDataSource object named DataSource1. This component provides an interface between a dataset component and data-aware controls on a form. In this sample, it is used to provide communication between the dataset and a TDBMemo object named DBMemo1. DBMemo1 is used to display the blobdata field of the dataset. To this end, the following setup is needed: The DataSet property of DataSource is set to qSelect. The DataSource property of DBMemo1 to DataSource1. The DataField property of DBMemo1 to blobdata. Once the main components are configured at design time you can run the application and interact with the sample in run time. To this end, the sample offers three buttons: Prepare data. This button creates an OnClick event that uses the TFileStream.Create method to instantiate the file stream in order to write a string into the file. Insert (external stream). This button creates an OnClick event that implements an external streaming. An external stream is provided by the application to FireDAC (external to FireDAC). Then, FireDAC reads this stream. See the code below: Insert (internal stream). This button creates an OnClick event that implements an internal streaming. An internal stream is provided by FireDAC to the application (internal to FireDAC). Then, the application reads this stream. To this end, the sample does the following: Use the StarTransaction method to start a mandatory transaction. Set the parameter DataType to ftStream. Set the parameter StreamMode to smOpenWrite in order to write the database BLOB value. Use the ExecSQL method to execute the SQL command. This will return the internal stream reference. Write the internal stream reference. Call the CloseStreams method to flush database API buffers and close internal streams. Use the Commint method to finish the transaction. For more information about this sample, please refer to the link below:http://docwiki.embarcadero.com/CodeExamples/Sydney/en/FireDAC.TFDQuery.BlobStreams_Sample Check out the full source code for the BLOB streams sample app in Windows for Delphi on GitHub.

Introduction Delphi Builder components for preparing and burning images to CD, DVD, and Blu-ray optical storage media. Uses standard Windows Image Mastering API 2. 2. Components in the Demo and what they do The Demo contains some labels with text, as well as TEdits for the directory paths and file names. The ‘Create Image’ button calls the button onClick event, which executes the Write process. In the next code you can see the execution in details. procedure TFormMain.ButtonCreateImageClick(Sender: TObject); begin Cancel := False; ProgressBar.Value := 0; UpdateControls(True); try FDiscImage.VolumeName := EditVolumeName.Text; FDiscImage.SourceTree := EditSourceTree.Text; FDiscImage.Write(EditImageName.Text); finally LabelStatus.Text := ”; UpdateControls(False); end; end; procedure TFormMain.ButtonCreateImageClick(Sender: TObject); begin   Cancel := False;   ProgressBar.Value := 0;   UpdateControls(True);   try     FDiscImage.VolumeName := EditVolumeName.Text;     FDiscImage.SourceTree := EditSourceTree.Text;     FDiscImage.Write(EditImageName.Text);   finally     LabelStatus.Text := ”;     UpdateControls(False);   end; end; The Main component that does the Image Writing is the TFDiscImage component by Winsoft. Depending on the TRadioGroup choice, the user chooses between two file systems – ISO 9660 and UDF. When one of the files systems is marked, an onChange event is fired with code: procedure TFormMain.RadioButtonChange(Sender: TObject); begin if RadioButtonIso9660.IsChecked then FDiscImage.FileSystems := [fsISO9660] else FDiscImage.FileSystems := [fsUDF]; end; procedure TFormMain.RadioButtonChange(Sender: TObject); begin   if RadioButtonIso9660.IsChecked then     FDiscImage.FileSystems := [fsISO9660]   else     FDiscImage.FileSystems := [fsUDF]; end; To get better vision on what these components do, check the video below: If you want to download this Component suite, click on the next link: https://winsoft.sk/fburncs.htm

procedure TFirebaseDatabase.SetBaseURI(const ABaseURI: string); begin   FBaseURI := ABaseURI; end; procedure TFirebaseDatabase.SetToken(const AToken: string); begin   FToken := AToken; end;   function TFirebaseDatabase.Get(const AParams: array of string;   AQueryParams: TDictionary<string, string> = nil): IFirebaseResponse; var   ARequest: IFirebaseRequest; begin   ARequest := TFirebaseRequest.Create(BaseURI, Token);   Result := ARequest.SendData(AParams, TFirebaseCommand.fcGet, nil,     AQueryParams); end;   function TFirebaseDatabase.Post(const AParams: array of string;   AData: TJSONValue = nil; AQueryParams: TDictionary<string, string> = nil;   ADataOwner: boolean = true): IFirebaseResponse; var   ARequest: IFirebaseRequest; begin   ARequest := TFirebaseRequest.Create(BaseURI, Token);   Result := ARequest.SendData(AParams, TFirebaseCommand.fcPost, AData,     AQueryParams, ADataOwner); end; function TFirebaseDatabase.Put(const AParams: array of string;   AData: TJSONValue = nil; AQueryParams: TDictionary<string, string> = nil;   ADataOwner: boolean = true): IFirebaseResponse; var   ARequest: IFirebaseRequest; begin   ARequest := TFirebaseRequest.Create(BaseURI, Token);   Result := ARequest.SendData(AParams, TFirebaseCommand.fcPut, AData,     AQueryParams, ADataOwner); end; function TFirebaseDatabase.Patch(const AParams: array of string;   AData: TJSONValue = nil; AQueryParams: TDictionary<string, string> = nil;   ADataOwner: boolean = true): IFirebaseResponse; var   ARequest: IFirebaseRequest; begin   ARequest := TFirebaseRequest.Create(BaseURI, Token);   Result := ARequest.SendData(AParams, TFirebaseCommand.fcPatch, AData,     AQueryParams, ADataOwner); end; function TFirebaseDatabase.Delete(const AParams: array of string;   AQueryParams: TDictionary<string, string> = nil): IFirebaseResponse; var   ARequest: IFirebaseRequest; begin   ARequest := TFirebaseRequest.Create(BaseURI, Token);   Result := ARequest.SendData(AParams, TFirebaseCommand.fcRemove, nil,     AQueryParams); end;

This industry-ready Order Entry Application template for busy small business owners. This project is to build a general template for the regular structure of the order entry application.       Specifics • Specifically we are working on something similar to general existing order entry applications. • The goal is to have a reusable template that a user can download and add their content to and create a professional-looking application. • The template will be delivered in a sample application that shows the power and flexibility of the template. And that is documented enough so that a user will understand how to customize it for their use. On the following slides, you will find screenshots and annotations Order Entry – tabs, rooms, and menu management Time Clock – employee clock in/out Manager – main manager settings Exit – exit from the application In a room view, it is possible to assign a table to a user and to start a new tab It is possible to move tables on the screen according to their real location It is possible to see the number of seats for each table On this screen, the user can pay for the order in different ways and leave tips You can download the Order Entry App from GetIt Package Manager Also, be sure to check out other amazing sample application here!